On Mar 4, 2014, at 2:30 PM, Richard Henderson <[email protected]> wrote:
> On 03/04/2014 01:23 AM, Richard Biener wrote:
>> Doesn't sound like a bug but a feature. We can move
>> asm ("" : : : "memory") around freely up to the next/previous
>> instruction involving memory.
>
> Asms without outputs are automatically volatile. So there ought be zero
> change
> with and without the explicit use of the __volatile__ keyword.
That’s what the documentation says but it wasn’t actually true as of a couple
of releases ago, as I recall.
paul
