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 rtl-optimization/63375] [4.8/4.9/5 Regression] reordering of reads across fences
Date: Mon, 24 Nov 2014 16:12:00 -0000	[thread overview]
Message-ID: <bug-63375-4-FWcL4Cl2jj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63375-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63375

--- Comment #15 from Richard Biener <rguenth at gcc dot gnu.org> ---
Note that the technical issue here is that the memory is considered as not
aliased and thus all barriers would need to explicitely reference it as
used and clobbered.


  parent reply	other threads:[~2014-11-24 16:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-25 23:08 [Bug rtl-optimization/63375] New: " bobby.prani at gmail dot com
2014-09-25 23:11 ` [Bug rtl-optimization/63375] " bobby.prani at gmail dot com
2014-09-26  0:35 ` [Bug tree-optimization/63375] " pinskia at gcc dot gnu.org
2014-09-26  8:18 ` [Bug tree-optimization/63375] [4.8/4.9/5 Regression] " rguenth at gcc dot gnu.org
2014-10-01 14:49 ` jamborm at gcc dot gnu.org
2014-10-02 16:49 ` jamborm at gcc dot gnu.org
2014-10-02 17:12 ` jamborm at gcc dot gnu.org
2014-10-02 17:14 ` jamborm at gcc dot gnu.org
2014-10-09  9:04 ` jakub at gcc dot gnu.org
2014-10-10 11:13 ` rguenth at gcc dot gnu.org
2014-11-10 17:34 ` [Bug rtl-optimization/63375] " bobby.prani at gmail dot com
2014-11-24 13:34 ` rguenth at gcc dot gnu.org
2014-11-24 15:03 ` bobby.prani at gmail dot com
2014-11-24 15:19 ` jakub at gcc dot gnu.org
2014-11-24 16:12 ` rguenth at gcc dot gnu.org [this message]
2014-11-24 19:32 ` bobby.prani at gmail dot com
2014-11-25 10:15 ` mikpelinux at gmail dot com

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-63375-4-FWcL4Cl2jj@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).