Re: Return value address

"Christoph Neubauer" <christoph.neubauer@siemens.com>
8 Sep 2004 12:07:05 -0400

          From comp.compilers
Related articles
Return value address nicolas_capens@hotmail.com (2004-09-07)
Re: Return value address christoph.neubauer@siemens.com (Christoph Neubauer) (2004-09-08)
Re: Return value address tmk@netvision.net.il (2004-09-13)
Re: Return value address Nicola.Musatti@ObjectWay.it (2004-09-14)
Re: Return value address christoph.neubauer@siemens.com (Christoph Neubauer) (2004-09-21)
Re: Return value address kamalp@acm.org (2004-09-21)
| List of all articles for this month |
From: "Christoph Neubauer" <christoph.neubauer@siemens.com>
Newsgroups: comp.compilers
Date: 8 Sep 2004 12:07:05 -0400
Organization: Siemens AG Austria
References: 04-09-054
Keywords: architecture, comment
Posted-Date: 08 Sep 2004 12:07:05 EDT

Hi Nic !


What about a stack model, that allocates:


r allways at 0
arguments starting at 4
local variables afterwards
temp variables afterwards


Hope that helps.
Chris


> Assuming x is stored at stack offset 0, and y at offset
> 4, t would be allocated at offset 8, and r at 12. The register
> allocator makes sure that the actual calculations happen with
> registers. The optimizer (which is actually before my register
> allocator) optimizes redundant copy operations (the last mov).
>
<snip>
[It also seemed to me that the obvious solution is for the caller to
allocate the return value cell. -John]

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.