On Fri, Jun 22, 2012 at 3:32 PM, Oliver Schmidt <ol.sc@web.de> wrote: > I do apologize for spamming the list about something so trivial. :3 > > Someone actively working on a new cc65 target is certainly entitled to > send messages to this list - be they trivial or not! At least in my > opinion... > > Ha! You may regret saying that. ;) I've come upon another head-scratcher, which makes me think I have my C stack set up wrongly somehow. Any insights would be extremely groovy, as I'm all out of ideas of what to look for. Hopefully it's not something as silly as last time. <_< The gist of it is, regular local variables seem to just not work, being unassignable -- always containing zero. Details of some specifics of the behavior I'm seeing are in a comment block in test.c . However, static local variables work just fine. I tried passing the -Cl switch to the compiler to make all variables static, but function parameters still don't work when I do that. That's what leads me to believe that I've got my C stack set up wrong. Whee, I wish I knew what I was doing! :3 Here are some files that may be elucidating. The POKEs around 0x310 are just writing characters sequentially into the display memory. Everything is built with -t none --cpu 65816 -Osir -g. test.c (containing main): http://pastebin.com/1e6809ja test.s: http://pastebin.com/sTw2Nq1R test.map: http://pastebin.com/a2qDtPxB rpc8e.cfg: http://pastebin.com/kCrZPQqk crt0.s: http://pastebin.com/K8fUgFBk mmu.s: http://pastebin.com/BzvhUk8p Thanks again. I really appreciate the time y'all take to help! ---------------------------------------------------------------------- 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 Jun 23 10:45:44 2012
This archive was generated by hypermail 2.1.8 : 2012-06-23 10:45:48 CEST