From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: Martin Jambor <mjambor@suse.cz>
Cc: Richard Biener <richard.guenther@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: RE: [PATCH] Change default for --param allow-...-data-races to off
Date: Mon, 23 Jun 2014 08:03:00 -0000 [thread overview]
Message-ID: <DUB118-W4683B0ED69FBB39F01AB5DE41F0@phx.gbl> (raw)
In-Reply-To: <20140620114418.GB24436@virgil.suse>
Hi,
On Fri, 20 Jun 2014 13:44:18, Martin Jambor wrote:
>
> Hi,
>
> On Thu, Jun 19, 2014 at 06:18:47PM +0200, Bernd Edlinger wrote:
>> Hi,
>>
>> from a recent discussion on gcc@gcc.gnu.org I have learned that the default of
>> --param allow-store-data-races is still 1, and it is causing problems.
>> Therefore I would like to suggest to change the default of this option to 0.
>
> I was about to propose a similar patch but I intended to leave the
> parameter set to one when -Ofast is specified so that benchmarks are
> not hurt by this and as a nice pointer for people exploring our
> options to really squeeze out 100% performance (which would of course
> mean documenting it too).
>
Well actually, I am not sure if we ever wanted to have a race condition here.
Have you seen any impact of --param allow-store-data-races on any benchmark?
Thanks
Bernd.
> Thanks,
>
> Martin
>
>>
>> Boot-strapped and regression tested on x86_64-linux-gnu.
>> Ok for trunk?
>>
>>
>> Thanks
>> Bernd.
>>
>
>> gcc/ChangeLog:
>> 2014-06-19 Bernd Edlinger <bernd.edlinger@hotmail.de>
>>
>> Set default for --param allow-...-data-races to off.
>> * params.def (PARAM_ALLOW_LOAD_DATA_RACES,
>> PARAM_ALLOW_STORE_DATA_RACES, PARAM_ALLOW_PACKED_LOAD_DATA_RACES,
>> PARAM_ALLOW_PACKED_STORE_DATA_RACES): Set default to off.
>>
>> testsuite/ChangeLog:
>> 2014-06-19 Bernd Edlinger <bernd.edlinger@hotmail.de>
>>
>> Adjust to new default for --param allow-...-data-races.
>> * c-c++-common/cxxbitfields-3.c: Adjust.
>> * c-c++-common/cxxbitfields-6.c: Adjust.
>> * c-c++-common/simulate-thread/bitfields-1.c: Adjust.
>> * c-c++-common/simulate-thread/bitfields-2.c: Adjust.
>> * c-c++-common/simulate-thread/bitfields-3.c: Adjust.
>> * c-c++-common/simulate-thread/bitfields-4.c: Adjust.
>> * g++.dg/simulate-thread/bitfields.C: Adjust.
>> * g++.dg/simulate-thread/bitfields-2.C: Adjust.
>> * gcc.dg/lto/pr52097_0.c: Adjust.
>> * gcc.dg/simulate-thread/speculative-store.c: Adjust.
>> * gcc.dg/simulate-thread/speculative-store-2.c: Adjust.
>> * gcc.dg/simulate-thread/speculative-store-3.c: Adjust.
>> * gcc.dg/simulate-thread/speculative-store-4.c: Adjust.
>> * gcc.dg/simulate-thread/strict-align-global.c: Adjust.
>> * gcc.dg/simulate-thread/subfields.c: Adjust.
>> * gcc.dg/tree-ssa/20050314-1.c: Adjust.
>>
>
>
next prev parent reply other threads:[~2014-06-23 8:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 16:18 Bernd Edlinger
2014-06-20 11:44 ` Martin Jambor
2014-06-23 8:03 ` Bernd Edlinger [this message]
2014-06-23 8:50 ` Richard Biener
2014-06-23 13:35 ` Bernd Edlinger
2014-06-24 20:19 ` Martin Jambor
2014-06-25 8:14 ` Richard Biener
2014-06-25 8:54 ` Jakub Jelinek
2014-06-25 8:56 ` Richard Biener
2014-06-25 9:48 ` Marc Glisse
2014-06-25 21:14 ` Jeff Law
2014-06-25 22:03 ` Martin Jambor
2014-06-26 6:43 ` Richard Biener
2014-06-26 7:53 ` Bernd Edlinger
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=DUB118-W4683B0ED69FBB39F01AB5DE41F0@phx.gbl \
--to=bernd.edlinger@hotmail.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=mjambor@suse.cz \
--cc=richard.guenther@gmail.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).