[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [avr-gcc-list] Gcc bug??
From: |
Brian Cuthie |
Subject: |
RE: [avr-gcc-list] Gcc bug?? |
Date: |
Wed, 10 Mar 2004 13:20:22 -0500 |
My humble suggestion would be to remove the extra layer of
abstraction/obfuscation and just let people delcare their functions NORETURN
or NAKED. While I love the efficiency that comes from macro'izing things I
agree that it's tough sometimes to remember what all of it means.
Anyway, AvrX is great. I really love it and appreciate your help.
Cheers,
Brian
> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden On Behalf Of Larry Barello
> Sent: Wednesday, March 10, 2004 12:49 PM
> To: address@hidden
> Subject: RE: [avr-gcc-list] Gcc bug??
>
>
> 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
>
_______________________________________________
avr-gcc-list mailing list
address@hidden
http://www.avr1.org/mailman/listinfo/avr-gcc-list