Aldy Hernandez writes:
> Can we treat this as a bugfix to be done during stage2? There is
> already some support in mainline, but it performs lousy on anything but
> the most simple of testccases. After much iterations with Richi, we
> couldn't come to an agreement on the remaining fixes. I wo
> It does not address other missing aspects of the c++ memory model. In
> particular, bitfields are still not compliant with not introducing new
> potential data races.
Can we treat this as a bugfix to be done during stage2? There is
already some support in mainline, but it performs lousy on an
On 10/27/2011 04:55 AM, Richard Guenther wrote:
I am really expecting this branch to be merged for 4.7. The current
status is very presentable IMHO.
If you get (or already got) ack from maintainers covering the areas you
touch then I am fine with merging this branch for 4.7 from a RM point
of
On Wed, Oct 26, 2011 at 6:31 PM, Benjamin Kosnik wrote:
>
>> Whats left
>> ===
>> Functionality is pretty much complete, but there are a few minor lose
>> ends still to deal with. They could be done after a merge, in the
>> next stage, or required before... you tell me :-)
>>
>> - potentia
On Wed, 26 Oct 2011, Andrew MacLeod wrote:
> Whats left
Out of interest, do you have any plans for the C1X side of things
(_Atomic, stdatomic.h etc.)? That would of course be for 4.8 or later.
--
Joseph S. Myers
jos...@codesourcery.com
> Whats left
> ===
> Functionality is pretty much complete, but there are a few minor lose
> ends still to deal with. They could be done after a merge, in the
> next stage, or required before... you tell me :-)
>
> - potentially implement -f[no]-inline-atomics (to never produce
> inline
On 26 October 2011 16:38, Andrew MacLeod wrote:
> I'd like to have the cxx-mem-model branch considered for merging with
> mainline before we end stage 1 for GCC 4.7.
>
> What it is
> ==
>
> GCC has had the __sync built-ins for atomic operations for a number of years
> now. They implement
I'd like to have the cxx-mem-model branch considered for merging with
mainline before we end stage 1 for GCC 4.7.
What it is
==
GCC has had the __sync built-ins for atomic operations for a number of
years now. They implement a "sequential consistent" (AKA seq-cst)
synchronization mod
