Thanks for the replies.
I am imagining a calling convention, usable in C via
__attribute__((...)), that does not preserve the caller's stack
pointer. I imagine that compiled Chicken code would interact well
with C using this convention. Been working a little (er, about 100
hours) on it. For
John Tobey scripsit:
I am imagining a calling convention, usable in C via
__attribute__((...)), that does not preserve the caller's stack
pointer.
Normally, what is preserved is the frame pointer and the return address.
You can suppress the frame pointer in gcc using the option
On Sat, Nov 13, 2010 at 2:30 PM, John Cowan co...@mercury.ccil.org wrote:
John Tobey scripsit:
I am imagining a calling convention, usable in C via
__attribute__((...)), that does not preserve the caller's stack
pointer.
Normally, what is preserved is the frame pointer and the return
