> -----Original Message----- > From: > avr-libc-dev-bounces+eweddington=cso.atmel....@nongnu.org > [mailto:avr-libc-dev-bounces+eweddington=cso.atmel....@nongnu. > org] On Behalf Of David Brown > Sent: Tuesday, March 17, 2009 4:19 PM > To: avr-libc-dev@nongnu.org > Subject: [avr-libc-dev] Re: Inline assembler and compiler optimization
> Googling for "gcc memory_barrier" suggests that it is a name > used in the > RTL patterns. Hmm. Need to look more into the machine description then. > The linux kernel uses names such as mb(), rmb() and wmb(), which are a > bit too short. On the architectures I looked at, these are defined to > be "barrier()", which for gcc is in turn defined as a volatile memory > clobber and for the intel compiler it is defined as the > __memory_barrier() builtin. > Well that's certainly one route. We could perhaps add it as a gcc builtin. Thanks for doing this research, David. :-) _______________________________________________ AVR-libc-dev mailing list AVR-libc-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/avr-libc-dev
