On Tue, 02 Oct 2007 18:08:32 +0400 Kirill Korotaev <[EMAIL PROTECTED]> wrote:
> Some gcc versions (I checked at least 4.1.1 from RHEL5 & 4.1.2 from > gentoo) can generate incorrect code with read_crX()/write_crX() > functions mix up, due to cached results of read_crX(). > I'm not so sure volatile is the right answer, as compared to giving the asm more strict contraints.... asm volatile tends to mean something else than "the result has changed".... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
