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 rtl-optimization/48774] [4.6/4.7 Regression] gcc-4.6.0 optimization regression on x86_64-unknown-linux-gnu Date: Thu, 28 Apr 2011 10:03:00 -0000 [thread overview] Message-ID: <bug-48774-4-TIpJsMJvDy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48774-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48774 --- Comment #4 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-04-28 10:02:22 UTC --- The code is fine with -fno-strict-aliasing, so I doubt that. Just -fno-gcse also doesn't fix it (nor does -fno-schedule-insns2, the usual RTL alias related miscompiler).
next prev parent reply other threads:[~2011-04-28 10:03 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-26 15:55 [Bug rtl-optimization/48774] New: " mariah.lenox at gmail dot com 2011-04-27 9:57 ` [Bug rtl-optimization/48774] [4.6/4.7 Regression] " rguenth at gcc dot gnu.org 2011-04-27 12:47 ` hjl.tools at gmail dot com 2011-04-27 19:08 ` xinliangli at gmail dot com 2011-04-28 10:03 ` rguenth at gcc dot gnu.org [this message] 2011-04-29 18:58 ` jakub at gcc dot gnu.org 2011-04-30 16:15 ` jakub at gcc dot gnu.org 2011-05-02 8:53 ` jakub at gcc dot gnu.org 2011-05-02 9:13 ` jakub at gcc dot gnu.org 2011-05-02 14:16 ` jakub at gcc dot gnu.org 2011-05-02 14:16 ` jakub at gcc dot gnu.org 2011-05-02 17:32 ` [Bug target/48774] " jakub at gcc dot gnu.org 2011-05-03 13:08 ` jakub at gcc dot gnu.org 2011-05-03 13:18 ` jakub at gcc dot gnu.org 2011-05-03 13:26 ` jakub at gcc dot gnu.org 2011-05-03 16:46 ` jakub at gcc dot gnu.org 2011-05-04 9:24 ` 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-48774-4-TIpJsMJvDy@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).