![]() | |||||||||||||
Messages in this thread |
Sergei Organov <osv@javad.com> wrote: > > +In addition, accesses to "volatile" memory locations and volatile asm > > +statements act as implicit compiler barriers. > > This last statement seems to contradict with what GCC manual says about > volatile asm statements: Perhaps I should say "compiler memory barrier", since it doesn't prevent instructions from being moved, but rather merely affects the ordering of memory accesses and volatile instructions. Hmmm... Is atomic_read() a compiler memory barrier? It isn't a CPU memory barrier, but it does touch explicitly volatile memory. David - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2006-03-14 20:37 [from the cache] ©2003-2008 | |||||||||||||