[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Bob Paddock
Subject: Re: [avr-libc-dev] Should cli() imply a memory barrier?
Date: Tue, 8 Jun 2010 10:21:11 -0400

> 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?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]