public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/51513] Only partially optimizes away __builtin_unreachable switch default case Date: Thu, 15 Dec 2011 01:28:00 -0000 [thread overview] Message-ID: <bug-51513-4-TBcTUiBUg8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51513-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51513 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |missed-optimization Status|UNCONFIRMED |NEW Last reconfirmed| |2011-12-15 Summary|[missed optimization] Only |Only partially optimizes |partially optimizes away |away __builtin_unreachable |unreachable switch default |switch default case |case | Ever Confirmed|0 |1 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> 2011-12-15 01:24:30 UTC --- Confirmed.
next prev parent reply other threads:[~2011-12-15 1:24 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-12 10:54 [Bug tree-optimization/51513] New: [missed optimization] Only partially optimizes away unreachable " sgunderson at bigfoot dot com 2011-12-12 11:04 ` [Bug tree-optimization/51513] " sgunderson at bigfoot dot com 2011-12-15 1:28 ` pinskia at gcc dot gnu.org [this message] 2012-12-11 21:54 ` [Bug tree-optimization/51513] Only partially optimizes away __builtin_unreachable " empann at hotmail dot com 2012-12-11 22:42 ` steven at gcc dot gnu.org 2014-02-28 1:37 ` pinskia at gcc dot gnu.org 2015-04-29 1:46 ` pinskia at gcc dot gnu.org 2015-04-29 2:25 ` bergner at gcc dot gnu.org 2015-04-29 14:58 ` bergner at gcc dot gnu.org 2020-04-07 23:09 ` mirq-gccboogs at rere dot qmqm.pl 2020-04-17 18:31 ` bergner 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-51513-4-TBcTUiBUg8@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).