tree fffa575916b27bac17dfb751300ed2e1f9107f0c
parent f891dd18c107d582c3ab98da5209c930e16baf78
author Kirill Korotaev <dev@openvz.org> 1192637073 +0200
committer Thomas Gleixner <tglx@inhelltoy.tec.linutronix.de> 1192644931 +0200

x86: mark read_crX() asm code as volatile

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().

The small app for x8664 below compiled with -O2 demonstrates this
(i686 does the same thing):