Hi Joseph, > If I create a function in assembler and declare it as __fastcall__, which is > responsible for popping the stack: the caller or the callee? General info on the cc65 calling sequence: http://www.cc65.org/doc/internal.txt Info on __fastcall__: http://www.cc65.org/doc/cc65-5.html __fastcall__ doesn't change the general behaviour. > What other stack > issues do I have to watch out for? Examples of needed function declarations > follow: > > unsigned char __fastcall__ foo1 (char*); Assembler funcions with 8-bit return value need to zero the X register on exit. Regards, Oliver ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Fri Feb 4 17:30:48 2011
This archive was generated by hypermail 2.1.8 : 2011-02-04 17:30:51 CET