I found the bug. It was due to an out-dated header for a library I need on multiple floppies at once. It works on the disk that holds the source for a library but not on the program that uses the library. I copied the necessary header, and that bug was fixed. Silly me! :( ----- Original Message ---- From: Joseph Rose <rose.joseph12@yahoo.com> To: cc65@musoftware.de Sent: Fri, February 4, 2011 11:19:28 AM Subject: [cc65] assembler/C stack issue If I create a function in assembler and declare it as __fastcall__, which is responsible for popping the stack: the caller or the callee? What other stack issues do I have to watch out for? Examples of needed function declarations follow: unsigned char __fastcall__ foo1 (char*); void __fastcall__ foo2 (char*, unsigned char); ------------ Joseph Rose, a.k.a. Harry Potter Working magic in the computer community...or at least syriving to! :( ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail. ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Sat Feb 19 21:05:01 2011
This archive was generated by hypermail 2.1.8 : 2011-02-19 21:05:04 CET