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 middle-end/56098] [4.6/4.7/4.8 Regression] conditional write through volatile pointer produces unintended read
Date: Fri, 25 Jan 2013 14:43:00 -0000 [thread overview]
Message-ID: <bug-56098-4-ZQTzkbb5jM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56098-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56098
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2013-01-25
CC| |matz at gcc dot gnu.org
Target Milestone|--- |4.6.4
Summary|conditional write through |[4.6/4.7/4.8 Regression]
|volatile pointer produces |conditional write through
|unintended read |volatile pointer produces
| |unintended read
Ever Confirmed|0 |1
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> 2013-01-25 14:42:43 UTC ---
This is cselim at work, preparing the way for if-conversion of the store ...
It shouldn't do this for volatiles of course.
Workaround: -fno-tree-cselim
next prev parent reply other threads:[~2013-01-25 14:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 18:22 [Bug c/56098] New: " werner at almesberger dot net
2013-01-25 8:43 ` [Bug middle-end/56098] " mikpe at it dot uu.se
2013-01-25 14:43 ` rguenth at gcc dot gnu.org [this message]
2013-01-25 15:35 ` [Bug middle-end/56098] [4.6/4.7/4.8 Regression] " jakub at gcc dot gnu.org
2013-01-25 20:04 ` jakub at gcc dot gnu.org
2013-01-25 20:06 ` [Bug middle-end/56098] [4.6/4.7 " jakub at gcc dot gnu.org
2013-01-25 22:46 ` werner at almesberger dot net
2013-01-26 2:10 ` werner at almesberger dot net
2013-02-01 14:17 ` jakub at gcc dot gnu.org
2013-02-01 14:38 ` [Bug middle-end/56098] [4.6 " jakub at gcc dot gnu.org
2013-02-27 19:47 ` pinskia at gcc dot gnu.org
2013-04-03 18:20 ` 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-56098-4-ZQTzkbb5jM@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).