public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/49140] [4.6 regression] wrong code with -O2 and -O3, not with -O3 -no-inline Date: Wed, 20 Jul 2011 09:24:00 -0000 [thread overview] Message-ID: <bug-49140-4-vBIzOq9b9o@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49140-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49140 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |NEW Known to fail| |4.6.1 --- Comment #16 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-07-20 09:22:45 UTC --- Confirmed. Works with -O0, fails with -O[12] at least. Still fails on the 4.6 branch. Compiling salsa.cpp with -O1 is enough to trigger the error, compiling salsa.cpp with -O0 is enough to mitigate it.
next prev parent reply other threads:[~2011-07-20 9:24 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-24 13:38 [Bug tree-optimization/49140] New: " doko at ubuntu dot com 2011-05-24 15:29 ` [Bug tree-optimization/49140] " rguenth at gcc dot gnu.org 2011-06-12 12:44 ` rguenth at gcc dot gnu.org 2011-06-12 14:29 ` hjl.tools at gmail dot com 2011-06-27 15:57 ` jakub at gcc dot gnu.org 2011-07-14 22:10 ` grokbrsm at free dot fr 2011-07-18 8:02 ` rguenth at gcc dot gnu.org 2011-07-18 10:20 ` doko at ubuntu dot com 2011-07-18 19:55 ` grokbrsm at free dot fr 2011-07-18 20:00 ` grokbrsm at free dot fr 2011-07-19 8:06 ` rguenth at gcc dot gnu.org 2011-07-19 16:13 ` grokbrsm at free dot fr 2011-07-19 16:15 ` grokbrsm at free dot fr 2011-07-20 6:08 ` grokbrsm at free dot fr 2011-07-20 7:11 ` grokbrsm at free dot fr 2011-07-20 8:45 ` rguenther at suse dot de 2011-07-20 9:24 ` rguenth at gcc dot gnu.org [this message] 2011-07-20 10:10 ` grokbrsm at free dot fr 2011-07-20 17:29 ` jakub at gcc dot gnu.org 2011-07-20 17:40 ` jakub at gcc dot gnu.org 2011-07-20 17:43 ` jakub at gcc dot gnu.org 2011-07-20 21:24 ` grokbrsm at free dot fr 2011-08-01 14:40 ` rguenth at gcc dot gnu.org 2011-10-16 14:40 ` mans at mansr dot com 2011-10-26 17:24 ` jakub at gcc dot gnu.org 2012-03-01 15:15 ` jakub at gcc dot gnu.org 2013-04-12 16:31 ` 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-49140-4-vBIzOq9b9o@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).