From: Peter Zijlstra <peterz@infradead.org>
To: Marek Polacek <polacek@redhat.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Martin Jambor <mjambor@suse.cz>, Petr Mladek <pmladek@suse.cz>,
linux-kernel@vger.kernel.org, gcc@gcc.gnu.org
Subject: Re: [PATCH] tell gcc optimizer to never introduce new data races
Date: Tue, 10 Jun 2014 17:13:29 +0200 [thread overview]
Message-ID: <20140610151329.GL6758@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20140610150455.GC7335@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 645 bytes --]
On Tue, Jun 10, 2014 at 05:04:55PM +0200, Marek Polacek wrote:
> On Tue, Jun 10, 2014 at 04:53:27PM +0200, Peter Zijlstra wrote:
> > On Tue, Jun 10, 2014 at 03:23:36PM +0200, Jiri Kosina wrote:
> > > +# Tell gcc to never replace conditional load with a non-conditional one
> > > +KBUILD_CFLAGS += $(call cc-option,--param allow-store-data-races=0)
> > > +
> >
> > Why do we not want: -fmemory-model=safe? And should we not at the very
> > least also disable packed-store-data-races?
>
> Note that the option does not exist, even though it is mentioned in the
> documentation.
Urgh.. ok. Any word on the packed-store-data thing?
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-06-10 15:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 13:23 [PATCH] tell gcc optimizer to never introduce new data races Jiri Kosina
2014-06-10 14:53 ` Peter Zijlstra
2014-06-10 15:04 ` Marek Polacek
2014-06-10 15:13 ` Peter Zijlstra [this message]
2014-06-10 15:17 ` Jakub Jelinek
2014-06-10 17:46 ` Linus Torvalds
2014-06-10 18:04 ` Steven Noonan
2014-06-10 18:54 ` Richard Biener
2014-06-10 18:10 ` Jiri Kosina
2014-06-16 10:29 ` Dan Carpenter
2014-06-16 10:52 ` Andreas Schwab
2014-06-16 11:20 ` Jiri Kosina
2014-06-16 14:37 ` Mark Brown
2014-06-17 7:58 ` Jiri Kosina
2014-08-20 23:27 ` Jiri Kosina
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=20140610151329.GL6758@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=gcc@gcc.gnu.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mjambor@suse.cz \
--cc=paulmck@linux.vnet.ibm.com \
--cc=pmladek@suse.cz \
--cc=polacek@redhat.com \
--cc=torvalds@linux-foundation.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