--- Comment #6 from eric dot weddington at atmel dot com 2009-08-07 16:38
---
The test case works for me on AVR GCC 4.3.2 using -Wall and -O[0123s]. Closing
bug.
--
eric dot weddington at atmel dot com changed:
What|Removed |Added
--- Comment #5 from abnikant dot singh at atmel dot com 2009-08-06 10:30
---
I guess this link can be of help
http://gcc.gnu.org/ml/gcc-patches/2003-12/msg01292.html [r28 and r29 frame
pointer]
--
abnikant dot singh at atmel dot com changed:
What|Removed
--- Comment #4 from wvangulik at xs4all dot nl 2008-01-10 19:00 ---
In 4.2.2 there is still no warning when compiling without -O.
void main(void)
{
volatile struct
{
int a, b, c, d, e, f;
} x;
x.d = 5;
asm volatile("in r28, 0x2F" : : : "r28");
x.d = 6;
}
--- Comment #3 from wvangulik at xs4all dot nl 2007-09-12 07:35 ---
(In reply to comment #2)
Ok I need some coffee...
The error IS generated when using -O[n] (so on -O as well)
Without specifing -O the compiler does not generate the warning.
--
http://gcc.gnu.org/bugzilla/show_bug.
--- Comment #2 from wvangulik at xs4all dot nl 2007-09-12 07:32 ---
(In reply to comment #1)
Hmm I cheated... I used -Os when compiling
Compiling without -O[n] gives no warning
Just tried compiling -O and then it does generate the error. It seems optimiser
flags triggers the warning?
-
--- Comment #1 from wvangulik at xs4all dot nl 2007-09-12 07:20 ---
Tested this against 4.1.2. The output for the given test case is different
(optimiser removed the useless loading):
/* prologue: frame size=0 */
push r28
/* prologue end (size=1) */
/* #APP */
in r28, 0x
