[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-libc-dev] Should cli() imply a memory barrier?
From: |
Joerg Wunsch |
Subject: |
Re: [avr-libc-dev] Should cli() imply a memory barrier? |
Date: |
Tue, 8 Jun 2010 21:39:51 +0200 |
User-agent: |
Mutt/1.5.20 (2009-06-14) |
As Jan Waclawek wrote:
> > _MemoryBarrier() (can sometimes be useful).
> Is this something already implemented in the compiler, or are you
> just preparing for future?
It's always been there: it's an empty inline asm instruction with a
"memory" clobber.
> Maybe this sounds trivial, but what about an exact definition of
> what the MemoryBarrier() is supposed to mean, first?
http://en.wikipedia.org/wiki/Memory_barrier
(The explanation there is a little CPU-centric, but similar aspects
also apply to the compiler.)
--
cheers, J"org .-.-. --... ...-- -.. . DL8DTL
http://www.sax.de/~joerg/ NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)
- Re: [avr-libc-dev] Should cli() imply a memory barrier?, Jan Waclawek, 2010/06/08
- Re: [avr-libc-dev] Should cli() imply a memory barrier?,
Joerg Wunsch <=
- Re: [avr-libc-dev] Should cli() imply a memory barrier?, Jan Waclawek, 2010/06/08
- Re: [avr-libc-dev] Should cli() imply a memory barrier?, Joerg Wunsch, 2010/06/08
- Re: [avr-libc-dev] Should cli() imply a memory barrier?, Jan Waclawek, 2010/06/08
- RE: [avr-libc-dev] Should cli() imply a memory barrier?, Weddington, Eric, 2010/06/08
- Re: [avr-libc-dev] Should cli() imply a memory barrier?, Joerg Wunsch, 2010/06/09