This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/38203] attribute `noreturn' isn't effective when -mthumb param is active
- From: "alexandre.nunes at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 28 Feb 2011 20:30:33 +0000
- Subject: [Bug target/38203] attribute `noreturn' isn't effective when -mthumb param is active
- Auto-submitted: auto-generated
- References: <bug-38203-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38203
--- Comment #6 from Alexandre Pereira Nunes <alexandre.nunes at gmail dot com> 2011-02-28 20:30:24 UTC ---
(In reply to comment #5)
> There's a lot of debate about whether the ARM behaviour is a good thing or not.
> Not pushing the return address means that the debugger cannot generate a
> back-trace in the event that the no-return function is something like abort();
> however, we could avoid pushing most of the other registers.
In a hosted environment, the tradeoff is clear. On a more constrained one, it
would depend on whether or not debugging is an option and if not, there's just
wasted stack. -f(no)omit-frame-pointer could be respected by the port, imho.