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

[Bob Paddock]

> This raises the question: Some years ago, a discussion about whether
> cli() should include a memory barrier ended with an agreement that
> it's not needed.

cli() should produce code of "least surprise".  Most people are
surprised when they find their explicitly placed cli() has been
(re)moved by code reordering.
atomic.h should be mentioned if the documentation route is the one
chosen.  Seems like there is some overlap here?