Messages in this thread | | | Date | Tue, 11 Nov 2014 16:36:06 -0800 | Subject | Re: compiler bug gcc4.6/4.7 with ACCESS_ONCE and workarounds | From | Linus Torvalds <> |
| |
On Tue, Nov 11, 2014 at 4:33 PM, Linus Torvalds <torvalds@linux-foundation.org> wrote: > > I guess as a workaround it is fine, as long as we don't lose sight of > trying to eventually do a better job.
Oh, and when it comes to the actual gcc bug - do you have any reason to believe that it's somehow triggered more easily by something particular in the arch/s390/kvm/gaccess.c code?
IOW, why does this problem not hit the x86 spinlocks that also use volatile pointers to aggregate types? Or does it?
Linus
| |