As Russell Shaw wrote: > Linux code has rmb() and wmb() for "read memory barrier" and "write > memory barrier", to solve that reordering problem. Something might > be learned from finding how those macros are defined.
They end up in a spaghetti of header files, but if my brain can trace that right, they simply end up in an __asm__ volatile(::"memory") unless the underlying CPU offers a better instruction to implement this. -- 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
