As Weddington, Eric wrote:
> > Anyway, it might make sense to provide an additional macro like
> > __memory_barrier() that expands to __asm__
> > __volatile__(""::"memory").
> If we do that, we might as well make it a public symbol, yes?:
> #define memory_barrier() __asm__ __volatile__(""::"memory")
If we document it, it /is/ public. ;-)
The point is that user programs might already use the identifier
memory_barrier so we'd better avoid redefining it (at least, as long
as it goes into one of the existing header files).
--
cheers, J"org .-.-. --... ...-- -.. . DL8DTL
http://www.sax.de/~joerg/ NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)
_______________________________________________
AVR-libc-dev mailing list
AVR-libc-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/avr-libc-dev
