summaryrefslogtreecommitdiffstats
path: root/security
diff options
context:
space:
mode:
authorAndrew Morton <akpm@osdl.org>2006-12-06 20:39:59 -0800
committerLinus Torvalds <torvalds@woody.osdl.org>2006-12-07 08:39:44 -0800
commitf1a60dbf68061e5a5364cbc723786b355637ffd3 (patch)
treeaa7f94e27e7fe110e2729ef1202b486442d1caa8 /security
parenta4ed06ad83acc3b7dafc018bc0b27469e787e27d (diff)
downloadop-kernel-dev-f1a60dbf68061e5a5364cbc723786b355637ffd3.zip
op-kernel-dev-f1a60dbf68061e5a5364cbc723786b355637ffd3.tar.gz
[PATCH] gcc-4.1.0 is bust
Keith says Compiling 2.6.19-rc6 with gcc version 4.1.0 (SUSE Linux), wait_hpet_tick is optimized away to a never ending loop and the kernel hangs on boot in timer setup. 0000001a <wait_hpet_tick>: 1a: 55 push %ebp 1b: 89 e5 mov %esp,%ebp 1d: eb fe jmp 1d <wait_hpet_tick+0x3> This is not a problem with gcc 3.3.5. Adding barrier() calls to wait_hpet_tick does not help, making the variables volatile does. And the consensus is that gcc-4.1.0 is busted. Suse went and shipped gcc-4.1.0 so we cannot ban it. Add a warning. Cc: Keith Owens <kaos@ocs.com.au> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud