RE: [avr-gcc-list] Gcc bug??

[Larry Barello]

Well, either you understand when a frame is generated, or you use noreturn
and avoid the issue altogether.  Over the years I have tended to opt for the
"no brainer" solution as it is hard to remember all the caveats for ultra
slim code.  Time to make a new release of the code and remove the naked
attribute...

-----Original Message-----
From: Brian Cuthie

Yup. My bad. Already changed tasks to NORETURN but didn't do the same for
interrupt handlers.

Seems to me, though, since you can ensure when the C compiler will and will
not use a frame pointer that using NAKED is risky, at best.

Thanks everyone.


_______________________________________________
avr-gcc-list mailing list
address@hidden
http://www.avr1.org/mailman/listinfo/avr-gcc-list