[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.00.1406161320180.1321@pobox.suse.cz>
Date: Mon, 16 Jun 2014 13:20:49 +0200 (CEST)
From: Jiri Kosina <jkosina@...e.cz>
To: Andreas Schwab <schwab@...e.de>
cc: Dan Carpenter <dan.carpenter@...cle.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Peter Zijlstra <peterz@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Martin Jambor <mjambor@...e.cz>, Petr Mladek <pmladek@...e.cz>,
linux-kernel@...r.kernel.org, gcc@....gnu.org,
linux-sparse@...r.kernel.org
Subject: Re: [PATCH] tell gcc optimizer to never introduce new data races
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists