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

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/

Follow-Ups:
- Re: [PATCH] mark read_crX() asm code as volatile
  - From: Kirill Korotaev <[email protected]>
- Re: [PATCH] mark read_crX() asm code as volatile
  - From: "H. Peter Anvin" <[email protected]>
- Re: [PATCH] mark read_crX() asm code as volatile
  - From: Chuck Ebbert <[email protected]>

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

Prev by Date: Re: [PATCH] ahci: Add MCP79 support to AHCI driver
Next by Date: Re: [PATCH] Fallback to ipv4 if we try to add join IPv4 multicast group via ipv4-mapped address.
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]