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

Arjan van de Ven wrote:

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"....

One of the aspect of volatility is "the result will change in ways you (gcc) just don't understand."

	-hpa
-
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]>
  • Re: [PATCH] mark read_crX() asm code as volatile
    • From: Arjan van de Ven <[email protected]>

• Prev by Date: Re: [git patch] SCSI aic94xx fix
• Next by Date: Re: [PATCH] Fix SH DMA API so it works with PVR cascade
• Previous by thread: Re: [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]