Re: [avr-libc-dev] Should cli() imply a memory barrier?

[Jan Waclawek]

> _MemoryBarrier() (can sometimes be useful).

Is this something already implemented in the compiler, or  are you just  
preparing for future?


> Are there any objections against adding it to cli(), or should we
> instead point out in the documentation that an explicit
> _MemoryBarrier() might be needed in order to get the expected results?

Maybe this sounds trivial, but what about an exact definition of what the 
MemoryBarrier() is supposed to mean, first?

JW