After looking at the assembly that my code is producing using fastcall, I realize that most of my functions are pushing the primary register back onto the stack anyway, I assume because I am not using the values passed to the function right away, but after some initializations and computations occur. So I guess in this case (with C functions, not hand-coded assembly) that fastcall would be doing an extra push onto the stack of the rightmost calling parameters? Am I correct in thinking that I have answer my own question about when not to use fastcall? -- Shawn __________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com ---------------------------------------------------------------------- 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 Nov 20 01:29:15 2004
This archive was generated by hypermail 2.1.8 : 2004-11-20 01:29:25 CET