[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 23:32:02 +0200 |
User-agent: |
Mutt/1.5.20 (2009-06-14) |
As Jan Waclawek wrote:
> I don't know what are "similar aspects".
It's a little unfair that you repost a message to the list which
you've sent me personally only before, and which I've already replied
to.
I won't have the time to craft a public reply as well, sorry.
--
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, 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?,
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?, Weddington, Eric, 2010/06/08
- Re: [avr-libc-dev] Should cli() imply a memory barrier?, Joerg Wunsch, 2010/06/09