From: Richard Guenther <richard.guenther@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Jeff Law <law@redhat.com>, Michael Matz <matz@suse.de>,
Aldy Hernandez <aldyh@redhat.com>,
Andrew MacLeod <amacleod@redhat.com>,
"Joseph S. Myers" <joseph@codesourcery.com>,
Richard Henderson <rth@redhat.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [cxx-mem-model] disallow load data races (1 of some)
Date: Fri, 25 Mar 2011 15:46:00 -0000 [thread overview]
Message-ID: <AANLkTimAypgNnemmG8q3UTEp=mv3bovaO973P4LT1heT@mail.gmail.com> (raw)
In-Reply-To: <20110325153338.GZ18914@tyan-ft48-01.lab.bos.redhat.com>
On Fri, Mar 25, 2011 at 4:33 PM, Jakub Jelinek <jakub@redhat.com> wrote:
> On Fri, Mar 25, 2011 at 09:30:22AM -0600, Jeff Law wrote:
>> I'm not going to chime in on this specific problem; however, it is worth
>> noting that many of the issues raised by the C++0x memory model also
>> affect the linux kernel.
>
> But what they are seeing are certainly store data races, not load races,
> because no hw they care about (or no hw at all?) detects the latter.
> Having options to avoid store data races is useful not just for C++0x memory
> model compliance and Linux kernel, but e.g. for OpenMP too.
And we have in the past removed code that created store data races
anyway. There is nothing new here.
As stated multiple times in the past things get "interesting" when you
look at non-x86 hardware.
Richard.
next prev parent reply other threads:[~2011-03-25 15:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 17:33 Aldy Hernandez
2011-03-24 19:58 ` Richard Henderson
2011-03-24 21:31 ` Aldy Hernandez
2011-03-24 21:51 ` Joseph S. Myers
2011-03-24 23:57 ` Andrew MacLeod
2011-03-25 10:03 ` Richard Guenther
2011-03-25 12:58 ` Aldy Hernandez
2011-03-25 15:27 ` Michael Matz
2011-03-25 15:33 ` Jeff Law
2011-03-25 15:35 ` Jakub Jelinek
2011-03-25 15:46 ` Richard Guenther [this message]
2011-03-29 16:52 ` Aldy Hernandez
2011-03-31 13:12 ` Jeff Law
2011-03-31 13:32 ` Richard Guenther
2011-03-31 13:32 ` Jeff Law
2011-03-31 21:07 ` Michael Matz
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='AANLkTimAypgNnemmG8q3UTEp=mv3bovaO973P4LT1heT@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=aldyh@redhat.com \
--cc=amacleod@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=law@redhat.com \
--cc=matz@suse.de \
--cc=rth@redhat.com \
/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).