Re: [PATCH] mark read_crX() asm code as volatile

On Tuesday 02 October 2007 16:08:32 Kirill Korotaev 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().

added thanks

-Andi



-
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/

---

• References:
  • [PATCH] mark read_crX() asm code as volatile
    • From: Kirill Korotaev <[email protected]>

• Prev by Date: Re: [discuss] [PATCH] Inconsistent mmap()/mremap() flags
• Next by Date: Re: [PATCH 07/30] IGET: Stop BEFS from using iget() and read_inode()
• Previous by thread: [PATCH] mark read_crX() asm code as volatile
• Next by thread: Re: [PATCH] mark read_crX() asm code as volatile
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]