Is there any workable combination of OS_main and the noreturn attribute,
that would prevent the compiler from inserting the _exit function?
In the ideal case six bytes would be saved.
My main() never returns, yet when I apply noreturn I'm told that
main() is returning a value.
Does
The OS_main and OS_task attributes are mainly used for RTOSes, for the
main() function and task functions respectively. However, OS_main can be
useful in an application's main() function that does not have an RTOS,
as it will reduce the code size slightly.
Is there any workable combination of
-Original Message-
From:
avr-gcc-list-bounces+eweddington=cso.atmel@nongnu.org
[mailto:avr-gcc-list-bounces+eweddington=cso.atmel@nongnu.
org] On Behalf Of Bob Paddock
Sent: Thursday, February 26, 2009 6:50 AM
To: AVR-GCC
Subject: Re: [avr-gcc-list] Re: [patch #6004
Anatoly Sokolov schrieb in avr-libc-devel:
The 'OS_main' attribute added in GCC 4.4.
The 'OS_main' patch for GCC 4.3 and 4.2 stored on WinAVR project SVN
repository.
Is there some documentation out there about the effect of all the AVR
specific attributes? I'd like to understand the puposes
Hi.
Is there some documentation out there about the effect of all the AVR
specific attributes? I'd like to understand the puposes and (generated
code) consequences of
OS_main
Function with OS_main and 'OS_task' attributes do not save any
call-saved registers.
1. OS_main attribute
-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
org] On Behalf Of Rolf Ebert
Sent: Monday, June 02, 2008 11:56 AM
To: 'AVR-GCC'
Subject: [avr-gcc-list] Re: [patch #6004] main-as-normal
patches for GCC
Anatoly Sokolov schrieb in avr-libc-devel
