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 regression/50472] Volatile qualification in data is not enough to avoid optimization over pointer to data Date: Mon, 26 Sep 2011 13:52:00 -0000 [thread overview] Message-ID: <bug-50472-4-lP47sD12t5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50472-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50472 --- Comment #5 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-09-26 12:59:02 UTC --- Author: rguenth Date: Mon Sep 26 12:58:35 2011 New Revision: 179196 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=179196 Log: 2011-09-26 Richard Guenther <rguenther@suse.de> PR tree-optimization/50472 * gimple-fold.c (fold_const_aggregate_ref_1): Do not fold volatile references. * gcc.dg/torture/pr50472.c: New testcase. Added: trunk/gcc/testsuite/gcc.dg/torture/pr50472.c Modified: trunk/gcc/ChangeLog trunk/gcc/gimple-fold.c trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2011-09-26 12:59 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-21 8:24 [Bug regression/50472] New: " Paulo.Matos at csr dot com 2011-09-21 9:41 ` [Bug regression/50472] " mikpe at it dot uu.se 2011-09-23 13:21 ` Paulo.Matos at csr dot com 2011-09-23 13:30 ` Paulo.Matos at csr dot com 2011-09-25 11:55 ` rguenth at gcc dot gnu.org 2011-09-26 13:52 ` rguenth at gcc dot gnu.org [this message] 2011-09-26 14:41 ` rguenth at gcc dot gnu.org 2011-09-26 14:42 ` [Bug tree-optimization/50472] " rguenth at gcc dot gnu.org 2012-06-12 2:33 ` amker 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-50472-4-lP47sD12t5@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).