public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xguo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/50078] [4.6 Regression] combine wrong code: volatile accesses optimized out
Date: Mon, 11 Jun 2012 09:51:00 -0000 [thread overview]
Message-ID: <bug-50078-4-1GzPIcwrFx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50078-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50078
--- Comment #16 from xuepeng guo <xguo at gcc dot gnu.org> 2012-06-11 09:51:12 UTC ---
Author: xguo
Date: Mon Jun 11 09:51:05 2012
New Revision: 188383
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=188383
Log:
2012-06-11 Terry Guo <terry.guo@arm.com>
Backport from mainline
2011-12-08 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/51466
* tree-ssa-forwprop.c (forward_propagate_addr_expr_1): Also copy
TREE_SIDE_EFFECTS.
2011-11-28 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/50078
* tree-ssa-forwprop.c (forward_propagate_addr_expr_1): Copy over
TREE_THIS_VOLATILE also from the old to new lhs resp. rhs.
Added:
branches/ARM/embedded-4_6-branch/gcc/testsuite/gcc.c-torture/execute/pr51466.c
branches/ARM/embedded-4_6-branch/gcc/testsuite/gcc.dg/pr50078.c
Modified:
branches/ARM/embedded-4_6-branch/gcc/ChangeLog.arm
branches/ARM/embedded-4_6-branch/gcc/testsuite/ChangeLog.arm
branches/ARM/embedded-4_6-branch/gcc/tree-ssa-forwprop.c
prev parent reply other threads:[~2012-06-11 9:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-14 0:57 [Bug c/50078] New: [4.6.1+ SVN 2011-08-13] ARM " khc at pm dot waw.pl
2011-08-14 9:24 ` [Bug c/50078] " mikpe at it dot uu.se
2011-08-14 9:39 ` rguenth at gcc dot gnu.org
2011-08-15 9:14 ` [Bug rtl-optimization/50078] [4.6/4.7 Regression] combine " rguenth at gcc dot gnu.org
2011-08-15 9:16 ` rguenth at gcc dot gnu.org
2011-08-17 21:28 ` jsm28 at gcc dot gnu.org
2011-09-05 11:49 ` steven at gcc dot gnu.org
2011-09-11 15:18 ` steven at gcc dot gnu.org
2011-09-11 15:26 ` steven at gcc dot gnu.org
2011-09-11 15:44 ` steven at gcc dot gnu.org
2011-09-11 16:28 ` steven at gcc dot gnu.org
2011-10-26 17:58 ` jakub at gcc dot gnu.org
2011-11-28 9:49 ` [Bug tree-optimization/50078] " jakub at gcc dot gnu.org
2011-11-28 21:10 ` jakub at gcc dot gnu.org
2011-11-28 21:11 ` [Bug tree-optimization/50078] [4.6 " jakub at gcc dot gnu.org
2011-12-09 11:34 ` jakub at gcc dot gnu.org
2011-12-10 16:40 ` mikpe at it dot uu.se
2011-12-12 17:38 ` jakub at gcc dot gnu.org
2012-06-11 9:51 ` xguo at gcc dot gnu.org [this message]
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-50078-4-1GzPIcwrFx@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: link
Be 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).