Mikael Magnusson <[EMAIL PROTECTED]> writes:
> Falk Hueffner wrote:
>> Hi,
>> the correct solution is to use __sync_synchronize as fallback, which
>> is a full memory barrier defined by gcc (starting from 4.1) for all
>> platforms. It is also desirable to use this on all platforms that
>> don't differentiate read/write/full barriers, since it gives the
>> compiler better opportunities to optimize.
>>
>
> Do you have a patch? I tried to use __sync_synchronize on i386, but it
> doesn't generate any synchronization code in the assembler output.
Sorry, you need __sync_synchronize(). (Does __sync_synchronize on its
own not generate a warning?)
--
Falk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
