> Can the fix be back ported?
Yes, the back port on 4.7 is straightforward, it just needs to be commited.
Yvan
On 29/11/12 15:42, Yvan Roux wrote:
Hi,
on ARMv7, the code generated for the __atomic_load builtins in the
__ATOMIC_ACQUIRE memory model, puts a memory barrier before the load, whereas
the semantic of the acquire memory model implies a barrier after.
The issue seems to be in expand_atomic_load
> If you can confirm you have a copyright assignment on file I can take care
> of checking it in.
Yes, I am covered by the copyright assignement RT 211150 between
STMicroelectronics and FSF.
Thanks,
Yvan
On 11/29/2012 10:42 AM, Yvan Roux wrote:
Hi,
on ARMv7, the code generated for the __atomic_load builtins in the
__ATOMIC_ACQUIRE memory model, puts a memory barrier before the load, whereas
the semantic of the acquire memory model implies a barrier after.
The issue seems to be in expand_atomic_
Hi,
on ARMv7, the code generated for the __atomic_load builtins in the
__ATOMIC_ACQUIRE memory model, puts a memory barrier before the load, whereas
the semantic of the acquire memory model implies a barrier after.
The issue seems to be in expand_atomic_load which puts a memory fence before
the l
