public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/53364] [4.7/4.8 Regression] Wrong code generation Date: Wed, 16 May 2012 08:54:00 -0000 [thread overview] Message-ID: <bug-53364-4-Y0XldavpNt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53364-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53364 --- Comment #4 from Marc Glisse <glisse at gcc dot gnu.org> 2012-05-16 07:11:35 UTC --- Looking at -fdump-tree-all, 081t.phicprop1 is still the same for -O1 and -O2, but O82t.dse1 is missing the memory writes for -O2.
next prev parent reply other threads:[~2012-05-16 7:11 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-15 19:24 [Bug c++/53364] New: " foom at fuhm dot net 2012-05-16 4:13 ` [Bug c++/53364] " foom at fuhm dot net 2012-05-16 4:28 ` pinskia at gcc dot gnu.org 2012-05-16 4:54 ` foom at fuhm dot net 2012-05-16 8:54 ` glisse at gcc dot gnu.org [this message] 2012-05-16 10:32 ` [Bug tree-optimization/53364] " rguenth at gcc dot gnu.org 2012-05-16 10:38 ` rguenth at gcc dot gnu.org 2012-05-16 11:22 ` rguenth at gcc dot gnu.org 2012-05-16 13:11 ` rguenth at gcc dot gnu.org 2012-05-16 13:13 ` rguenth at gcc dot gnu.org 2012-05-16 13:19 ` rguenth 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-53364-4-Y0XldavpNt@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).