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 middle-end/50385] missed-optimization: jump to __builtin_unreachable() not removed Date: Fri, 11 Nov 2011 01:39:00 -0000 [thread overview] Message-ID: <bug-50385-4-2iLBbqACvz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50385-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50385 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |missed-optimization Status|UNCONFIRMED |NEW Last reconfirmed| |2011-11-11 Component|tree-optimization |middle-end Ever Confirmed|0 |1 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2011-11-11 00:39:55 UTC --- Confirmed with a much simpler testcase: int f (int i) { if (i <= 1) return 1; __builtin_unreachable(); } --- CUT --- I found this while adding a basic block reordering pass to the tree level and I got a failure with builtin-unreachable-2.c .
next prev parent reply other threads:[~2011-11-11 0:40 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-13 15:21 [Bug tree-optimization/50385] New: " wouter.vermaelen at scarlet dot be 2011-11-11 1:39 ` pinskia at gcc dot gnu.org [this message] 2013-09-08 8:10 ` [Bug middle-end/50385] " glisse at gcc dot gnu.org 2015-02-24 20:54 ` law at redhat dot com
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-50385-4-2iLBbqACvz@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).