Shoddy Compilers
Last Friday I got an email saying that the old compiler we use at work is actually generating the test/branch code in this snippet:
do {
/* foo */
} while (0);
I signed, recited the habitual "crappy IAR" line, and blamed someone not turning on the optimiser.
Until now. I tried with the new "improved optimiser" compiler they sent us, which is supposed to be a lot better. The compiler isn't as brain-dead as the older one, which is nice. However, this new optimiser still sucks:
main:
?0012:
LDI R16,LOW(?0013)
LDI R17,HIGH(?0013)
LDI R18,(?0013 >> 16)
CALL puts
LDI R16,LOW(0)
TST R16
BRNE ?0012
RET
Oh wonderful. This is with full size optimisations, and the result is the same with full speed optimisations. Curse the proprietary world and their shoddy compilers!
Posted by Tom Parker at Mon May 10 19:45:53 2004:
The "shoody compilers" link gets me
'Error: I'm afraid this is the first I've heard of a "txt" flavoured pyblosxom.
Try dropping the "?flav=txt" bit from the end of the URL.'
Dropping the .txt fixes the problem
Posted by Ross at Mon May 10 20:00:32 2004:
'Error: I'm afraid this is the first I've heard of a "txt" flavoured pyblosxom.
Try dropping the "?flav=txt" bit from the end of the URL.'
Dropping the .txt fixes the problem
