Re: [cc65] assembler/C stack issue

From: Payton Byrd <plbyrd1gmail.com>
Date: 2011-02-04 17:26:20
On Fri, Feb 4, 2011 at 10:19 AM, Joseph Rose <rose.joseph12@yahoo.com>wrote:

> 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);
>

I'll give you the same advice that I received the first time I had this
question.  Write a stub method in C and compile it with the debug option
turned on using cc65 and then use the resulting .s file as the starting
point for your assembler functions.

-- 
Payton Byrd
<http://www.paytonbyrd.com>
<http://it.toolbox.com/blogs/paytonbyrd>

----------------------------------------------------------------------
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:26:28 2011

This archive was generated by hypermail 2.1.8 : 2011-02-04 17:26:30 CET