[cc65] Compiler code generation bug?

Hi all,

I was finally able to repair my 16K RAM card in my Apple II+, but I might have tripped over a code generation bug in the process.  I first noticed that something was amiss when  an expected/actual comparison failed and yet the data values were identical!  I found a few workarounds but I thought I should float it here for some helpful clarification...  ;-)

Attached please find the C source and a compiler-generated assembly file.  There are comments in the C source describing what appear to be some problems in the generated assembly that caused the incorrectly failed comparisons.

Insights welcomed!


Thanks,
Dave



----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.