From: Jiri Kosina <jkosina@suse.cz>
To: Andreas Schwab <schwab@suse.de>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Peter Zijlstra <peterz@infradead.org>,
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,
linux-sparse@vger.kernel.org
Subject: Re: [PATCH] tell gcc optimizer to never introduce new data races
Date: Mon, 16 Jun 2014 13:20:49 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.1406161320180.1321@pobox.suse.cz> (raw)
In-Reply-To: <mvmsin51605.fsf@hawking.suse.de>
On Mon, 16 Jun 2014, Andreas Schwab wrote:
> > Adding "--param allow-store-data-races=0" to the GCC options for the
> > kernel breaks C=1 because Sparse isn't expecting a GCC option with that
> > format.
>
> Please try --param=allow-store-data-races=0 instead.
How reliable is this format across GCC versions? GCC manpage doesn't seem
to list it as a valid alternative.
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2014-06-16 11:20 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
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 [this message]
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=alpine.LNX.2.00.1406161320180.1321@pobox.suse.cz \
--to=jkosina@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@oracle.com \
--cc=gcc@gcc.gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=mjambor@suse.cz \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.cz \
--cc=schwab@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.