Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| [Q:] tail calls and parameter passing reig@dcs.gla.ac.uk (Fermin Reig) (1998-11-19) |
| Re: [Q:] tail calls and parameter passing gary@wheel.tiac.net (1998-11-21) |
| Re: [Q:] tail calls and parameter passing ramsdell@linus.mitre.org (John D. Ramsdell) (1998-11-21) |
| Re: [Q:] tail calls and parameter passing monnier+comp/compilers/news/@tequila.cs.yale.edu (Stefan Monnier) (1998-11-24) |
| Re: [Q:] tail calls and parameter passing bijuthom@ibm.net (Biju Thomas) (1998-11-24) |
| From: | Stefan Monnier <monnier+comp/compilers/news/@tequila.cs.yale.edu> |
| Newsgroups: | comp.compilers |
| Date: | 24 Nov 1998 22:18:51 -0500 |
| Organization: | Compilers Central |
| References: | 98-11-090 98-11-107 |
| Keywords: | code, design, comment |
> calling conventions. The one I've looked into a bit, namely the
> AIX/RS6K C calling convention, allocates a fairly large fixed sized
> stack frame for any function which calls another one, so there
> should be space there in any case. So the tail call code in G could
Reminds me of a question (that indeed popped up when I had to look at
the AIX calling convention): is there any paper describing the
rationale (and experiments) behind this or that calling convention ?
Stefan
[I think the RS6000 technology book said something about it. -John]
Return to the
comp.compilers page.
Search the
comp.compilers archives again.