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
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
Hi all,
Anyone know of an active project or system other than Chicken that uses the
machine's stack in a similar way?
Curious,
John
___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users
