public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/53294] New: Optimize out some exception code Date: Wed, 09 May 2012 10:40:00 -0000 [thread overview] Message-ID: <bug-53294-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53294 Bug #: 53294 Summary: Optimize out some exception code Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: glisse@gcc.gnu.org Hello, it would be great if the compiler could transform code like: try { throw 42; } catch(...) { } into nothing (or in practice into a simple goto, since there will be code around). It already knows to remove the code after "throw", it could statically check that the exception will be caught locally and thus skip the __cxa_throw, __cxa_begin_catch game. Filed as C++ front-end, but it might be for the middle-end, since it would be best if this optimization happened after inlining.
next reply other threads:[~2012-05-09 10:37 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-09 10:40 glisse at gcc dot gnu.org [this message] 2012-05-09 14:36 ` [Bug c++/53294] " rguenth at gcc dot gnu.org 2021-07-23 0:12 ` pinskia at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-53294-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).