Related articles |
---|
Compiler Terminology pgupt@ece.arizona.edu (Pallav Gupta) (2002-07-04) |
Re: Compiler Terminology peter_flass@yahoo.com (Peter Flass) (2002-07-15) |
Re: Compiler Terminology journeyman@compilerguru.com (journeyman) (2002-07-15) |
From: | "Peter Flass" <peter_flass@yahoo.com> |
Newsgroups: | comp.compilers |
Date: | 15 Jul 2002 23:43:47 -0400 |
Organization: | Road Runner |
References: | 02-07-029 |
Keywords: | design, registers |
Posted-Date: | 15 Jul 2002 23:43:46 EDT |
Depends. What's the language/OS convention. *Someone* should save all
the registers the callee uses, but it could be the caller, the callee,
or both. For example the OS/390 convention is that the called program
saves all the registers.
Pallav Gupta wrote:
> Now my understanding is that between a function call, the compiler
> should generally save/restore ALL registers that the callee function
> uses. Correct? (Ofcourse there can be some global registers that need
> not be saved/restored say for instance the stack pointer)
Return to the
comp.compilers page.
Search the
comp.compilers archives again.