--- Ullrich von Bassewitz <uz@musoftware.de> wrote: > The optimizer is removing the test because it knows > you stored a one in this > place before. And yes, it is allowed to do that. Is this optimization intended for other similiar cases as well? It seems that in this case the programmer is making an conscious choice to test for the same value immediately after storing it, and the compiler is helping too much. I solved my immediate problem by moving the store up several lines in the code, which seems to force the compiler to reload it and compare. I guess the optmizer only knows about so many previous instructions? > * Place the stuff into a small assembler module. This is probably the best easiest to understand (for me) solution. Thanks, Uz. __________________________________ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Thu Jul 15 15:40:48 2004
This archive was generated by hypermail 2.1.8 : 2004-07-15 15:40:58 CEST