Imagecraft ICCAVR & ANSI Standards compliance

Nov 16, 2003 1 Replies

Hi everyone.



I have found what I consider to be a deficiency, if not a bug, in the ImageCraft ICCAVR C-compiler, ver 6.29. I would like to find out if what I consider to be a bug makes this compiler non-ANSI C complaint or not and what others here feel about my discovery.



I have e-mailed the author (please see my text at the end) but he does not feel this issue makes the compiler non-ANSI complaint and did not express an interest in changing the behavior.



The issue is that the compiler seems to always encode an immediate as an int data type (int on the AVR is 16-bits) and does not check the lvalue datatype (to see if it is something other than an int) during variable declarations or even usage in some cases.



As an example the following declaration:



long my_long_variable = (1


I would like to apologize, this message was meant for comp.arch.embedded and I accidentally posted it in here.

Sorry to everyone for the off-topic posting.

Vincent.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required