public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/55981] std::atomic store is split in two smaller stores
Date: Tue, 15 Jan 2013 20:02:00 -0000	[thread overview]
Message-ID: <bug-55981-4-C0fSk1yWYO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55981-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55981

--- Comment #10 from Uros Bizjak <ubizjak at gmail dot com> 2013-01-15 20:01:41 UTC ---
(In reply to comment #9)
> (In reply to comment #4)
> > (In reply to comment #2)
> > > Btw, the same happens if atomic is replaced with "volatile unsigned long y" -
> > > which does not violate the standard, but may be considered undesirable by some.
> > > I don't have a strong opinion about this.
> > 
> > This really does need to be fixed in the "volatile unsigned long y" case, or
> > device drivers storing constants to device registers will break.  So please fix
> > this for volatiles as well as atomics.
> 
> Please open a new PR for this.

It looks to me that volatiles should not be allowed as offsetable operands, but
let's discuss this in a separate PR.


  parent reply	other threads:[~2013-01-15 20:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14 22:39 [Bug other/55981] New: " eugeni.stepanov at gmail dot com
2013-01-14 22:46 ` [Bug other/55981] " eugeni.stepanov at gmail dot com
2013-01-14 22:48 ` eugeni.stepanov at gmail dot com
2013-01-14 23:08 ` pinskia at gcc dot gnu.org
2013-01-15 12:30 ` [Bug target/55981] " paulmck at linux dot vnet.ibm.com
2013-01-15 14:22 ` ubizjak at gmail dot com
2013-01-15 14:26 ` ubizjak at gmail dot com
2013-01-15 14:30 ` ubizjak at gmail dot com
2013-01-15 19:38 ` ubizjak at gmail dot com
2013-01-15 19:39 ` ubizjak at gmail dot com
2013-01-15 20:02 ` ubizjak at gmail dot com [this message]
2013-01-17 16:25 ` uros at gcc dot gnu.org
2013-01-17 22:51 ` uros at gcc dot gnu.org
2013-01-17 22:54 ` ubizjak at gmail dot com
2014-02-16 13:14 ` jackie.rosen at hushmail 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-55981-4-C0fSk1yWYO@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).