This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: backporting PR52558 to 4.7?
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Aldy Hernandez <aldyh at redhat dot com>
- Cc: "Joseph S. Myers" <joseph at codesourcery dot com>, Richard Guenther <rguenther at suse dot de>, GCC Mailing List <gcc at gcc dot gnu dot org>, Torvald Riegel <triegel at redhat dot com>
- Date: Thu, 7 Jun 2012 20:25:30 +0200
- Subject: Re: backporting PR52558 to 4.7?
- References: <4FC7D828.5060506@redhat.com> <4FD0E976.8050500@redhat.com>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Thu, Jun 07, 2012 at 12:48:38PM -0500, Aldy Hernandez wrote:
> On 05/31/12 15:44, Aldy Hernandez wrote:
> >Hello gentlemen.
> >
> >Would it be ok to backport the fix for PR52558 into the 4.7 branch? This
> >PR is the store data race patch I have been iterating with Richi. Doing
> >so will avoid critical data races for both TM and the C++ memory model.
> >
> >The code is all predicated by flag_tm or !PARAM_VALUE
> >(PARAM_ALLOW_STORE_DATA_RACES)), so it shouldn't affect code paths
> >outside of TM or the C++1x memory model.
> >
> >Thanks.
> Ping.
I think it is ok for 4.7.2, 4.7.1 is frozen now and it isn't as severe as
various other PRs we've also deferred for 4.7.2.
Jakub