Messages in this thread | | | From | Sergei Organov <> | Subject | Re: [PATCH] Document Linux's memory barriers [try #4] | Date | Wed, 15 Mar 2006 12:11:57 +0300 |
| |
David Howells <dhowells@redhat.com> writes:
> 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.
Well, I'd just remove the two lines in question as neither volatile access nor volatile asm are barriers, -- that's why the barrier() is needed in the first place.
-- Sergei. - 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/
| |