This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug target/56165] Missed optimization for 'noreturn' functions


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56165

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-01-31 17:35:34 UTC ---
This is intentional, often from within a noreturn function such as abort you
want to do a backtrace and get an accurrate backtrace.  Also, even noreturn
functions can throw, even if not caught immediately in the caller, so you can't
trash call saved registers.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]