public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/49073] g++ optimizer breaks do-while code Date: Fri, 20 May 2011 07:56:00 -0000 [thread overview] Message-ID: <bug-49073-4-xZc6z1corG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49073-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49073 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2011.05.20 06:57:01 CC| |jakub at gcc dot gnu.org Version|4.5.2 |4.6.0 Ever Confirmed|0 |1 --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-05-20 06:57:01 UTC --- Confirmed for 4.6 and trunk, if you can reproduce it with 4.5, complain to Ubuntu for backporting very risky patch that caused already more than one regression. Caused by http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=160445 Simplified testcase: extern void abort (void); int c; int main () { int a[] = { 1, 2, 3, 4, 5, 6, 7 }, d = 1, i = 1; _Bool f = 0; do { d = a[i]; if (f && d == 4) { ++c; break; } i++; f = (d == 3); } while (d < 7); if (c != 1) abort (); return 0; } I'll have a look.
next prev parent reply other threads:[~2011-05-20 7:27 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-20 1:38 [Bug c++/49073] New: " pjr at itee dot uq.edu.au 2011-05-20 7:56 ` jakub at gcc dot gnu.org [this message] 2011-05-20 8:11 ` [Bug c++/49073] " jakub at gcc dot gnu.org 2011-05-20 10:01 ` [Bug tree-optimization/49073] [4.6/4.7 Regression] " jakub at gcc dot gnu.org 2011-05-20 10:33 ` jakub at gcc dot gnu.org 2011-05-20 14:52 ` jakub at gcc dot gnu.org 2011-05-20 14:59 ` jakub at gcc dot gnu.org 2011-05-20 15:05 ` jakub 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-49073-4-xZc6z1corG@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).