public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Andrea Parri <andrea.parri@amarulasolutions.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Josh Triplett <josh@joshtriplett.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFR] Store tearing
Date: Sun, 28 Oct 2018 18:20:42 -0700	[thread overview]
Message-ID: <20181029012042.GR4170@linux.ibm.com> (raw)
In-Reply-To: <20181028231003.GA4021@andrea>

On Mon, Oct 29, 2018 at 12:10:03AM +0100, Andrea Parri wrote:
> Hopefully, with Paul's proper email address this time,
> 
>   Andrea
> 
> On Mon, Oct 29, 2018 at 12:06:27AM +0100, Andrea Parri wrote:
> > Hi,
> > 
> > memory-barriers.txt says:
> > 
> >   [on "store tearing"]
> > 
> >   "In fact, a recent bug (since fixed) caused GCC to incorrectly use
> >    this optimization in a volatile store.".
> > 
> > I was wondering if you could help me retrieve some reference/discussions
> > about this?

This was quite some time ago, but it involved a 32-bit volatile store
of a constant such as 0x10001.  The machine in question had a narrow
store-immediate instruction, so the compiler emitted  a pair of 16-bit
store-immediate instructions.  This bug was fixed, though only after
significant screaming and shouting.

							Thanx, Paul


  reply	other threads:[~2018-10-29  1:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-28 23:06 [RFR] Store tearing Andrea Parri
2018-10-28 23:10 ` Andrea Parri
2018-10-29  1:20   ` Paul E. McKenney [this message]
2018-10-29  5:16     ` Andrea Parri
2018-10-29  9:23     ` Arnd Bergmann
2018-10-29 11:27       ` Paul E. McKenney

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=20181029012042.GR4170@linux.ibm.com \
    --to=paulmck@linux.ibm.com \
    --cc=andrea.parri@amarulasolutions.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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