On Mon, Oct 29, 2018 at 10:23:07AM +0100, Arnd Bergmann wrote:
> On Mon, Oct 29, 2018 at 2:21 AM Paul E. McKenney
> wrote:
> >
> > 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, Oc
On Mon, Oct 29, 2018 at 2:21 AM Paul E. McKenney wrote:
>
> 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-b
On Sun, Oct 28, 2018 at 06:20:42PM -0700, Paul E. McKenney wrote:
> 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,
> > >
> >
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 r
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 vola
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?
Thanks,
Andrea
6 matches
Mail list logo