http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52301
--- Comment #6 from rickyrockrat 2012-02-22
05:05:56 UTC ---
I guess I'm a little confused. How can GCC NOT know it can change?
Any RAM location not only can but usually does change. It seems that volatile
should be the norm.
Whatever. I'll jus
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52301
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52301
--- Comment #4 from rickyrockrat 2012-02-22
04:31:11 UTC ---
Created attachment 26724
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26724
Assembly generated using script and original source
Resulting assembly from recently supplied files -
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52301
--- Comment #3 from rickyrockrat 2012-02-22
04:29:21 UTC ---
Created attachment 26723
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26723
Script to compile bug52301.c
Script to run avr-gcc on the subject file.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52301
--- Comment #2 from rickyrockrat 2012-02-22
04:27:01 UTC ---
Created attachment 26722
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26722
Intermediate file
Intermediate file, as requested. Changed name to bug52301.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52301
--- Comment #1 from Andrew Pinski 2012-02-21
03:42:56 UTC ---
Can you provide the preprocessed source? Add -save-temps and attach the .i
file?
Also can you run "avr-gcc -v" and provide the output of that?
