From: locke AT mcs DOT net (Peter Johnson) Newsgroups: comp.os.msdos.djgpp Subject: Re: Historical: Use of recursion Date: Wed, 15 Dec 1999 10:54:49 -0600 Organization: BiLogic Productions Lines: 33 Message-ID: References: <82vfqn$6ce$1 AT mango DOT singnet DOT com DOT sg> <830qak$s8k AT tandem DOT CAM DOT ORG> NNTP-Posting-Host: isr4186.urh.uiuc.edu X-Newsreader: MicroPlanet Gravity v2.12 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com In article , NOSP AT Musenet says... > "Martin Peach" wrote: > > > > An architecture that uses a separate memory space for > > the stack would be preferable, but that doesn't seem to > > be in the works, > > Mostly because programs need access to their stack > through a register, and Intel severely lacks registers. > Enter PowerPC. Thirty-two 32-bit integer registers. > Velocity Engine(tm) on the G4 makes the CPU a > 128-bit powerhouse. No wonder the latest Power > Macintosh computers are personal supercomputers. > But this is swinging way off-topic in a c.o.m.* newsgroup. Going even more off-topic: Take a look at Intel's IA-64 architecture--it has a processor managed register stack (!). The processor has an enormous number of registers: 128 64-bit GP integer registers, 128 80-bit FP registers, and 64 1-bit predicate registers. The integer registers can be "allocated" (there's actually an opcode called "alloc") by subroutines to give local, input, and output register space for parameter passing and local variables. The processor actually has a unit which manages internal register "stack" frames and automatically moves the oldest ones out to RAM. The whole thing has a feeling (to a computer engineer) of being truly _designed_ like no other processor to date. I'm looking forward to owning one :). -- Peter Johnson locke AT mcs DOT net :Windows: Where do you want to go today? :Linux: Where do you want to go tomorrow? :FreeBSD: Are you guys coming or what?