https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55139
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55139
--- Comment #6 from Jonathan Wakely ---
This was fixed for 4.8.0 by r193363, right?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55139
--- Comment #5 from ak at gcc dot gnu.org 2012-11-09 15:24:32 UTC ---
Author: ak
Date: Fri Nov 9 15:24:25 2012
New Revision: 193363
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=193363
Log:
Handle target specific memory models
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55139
--- Comment #4 from Andi Kleen 2012-11-09
14:06:20 UTC ---
My earlier analysis was not correct. I was chasing the wrong warning.
Rather the problem is in c-common.c, where the atomic models are checked again.
I'm sending a patch for that.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55139
--- Comment #3 from Andi Kleen 2012-11-07
14:45:17 UTC ---
I saw the problem both with bootstrapped and non bootstrapped (4.6 base)
compilers
I haven't checked if it's always the missing and, but it's likely
Ok I can change everything t
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55139
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Co
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55139
--- Comment #1 from Andi Kleen 2012-11-07
04:03:53 UTC ---
This is an interesting one. This is the gcc code:
enum memmodel
{
MEMMODEL_RELAXED = 0,
MEMMODEL_CONSUME = 1,
MEMMODEL_ACQUIRE = 2,
MEMMODEL_RELEASE = 3,
MEMMODEL_
