public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/49671] [4.6/4.7 Regression] volatile goes missing after inlining Date: Tue, 26 Jul 2011 05:29:00 -0000 [thread overview] Message-ID: <bug-49671-4-DbsA0BVVNH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49671-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49671 --- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> 2011-07-26 05:28:50 UTC --- Author: pinskia Date: Tue Jul 26 05:28:45 2011 New Revision: 176782 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=176782 Log: 2011-07-25 Andrew Pinski <apinski@cavium.com> PR tree-opt/49671 * tree-inline.c (remap_gimple_op_r): Copy TREE_THIS_VOLATILE and TREE_THIS_NOTRAP into the inner most MEM_REF. Always copy TREE_THIS_VOLATILE. * tree-sra.c (ptr_parm_has_direct_uses): Check that the lhs, rhs and arguments are not volatile references. 2011-07-25 Andrew Pinski <apinski@cavium.com> PR tree-opt/49671 * gcc.dg/tree-ssa/pr49671-1.c: New testcase. * gcc.dg/tree-ssa/pr49671-2.c: New testcase. Added: trunk/gcc/testsuite/gcc.dg/tree-ssa/pr49671-1.c trunk/gcc/testsuite/gcc.dg/tree-ssa/pr49671-2.c Modified: trunk/gcc/ChangeLog trunk/gcc/testsuite/ChangeLog trunk/gcc/tree-inline.c trunk/gcc/tree-sra.c
next prev parent reply other threads:[~2011-07-26 5:29 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-07 21:39 [Bug middle-end/49671] New: " pinskia at gcc dot gnu.org 2011-07-07 21:41 ` [Bug middle-end/49671] [4.6/4.7 Regression] " pinskia at gcc dot gnu.org 2011-07-07 22:49 ` pinskia at gcc dot gnu.org 2011-07-07 23:07 ` pinskia at gcc dot gnu.org 2011-07-08 10:31 ` rguenth at gcc dot gnu.org 2011-07-26 5:29 ` pinskia at gcc dot gnu.org [this message] 2011-07-26 7:52 ` pinskia at gcc dot gnu.org 2011-07-26 7:53 ` pinskia 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-49671-4-DbsA0BVVNH@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).