Don't use '-fwrapv' compiler option: it's buggy in gcc-4.1.x
authorLinus Torvalds <torvalds@linux-foundation.org>
Sun, 12 Jul 2009 18:25:04 +0000 (11:25 -0700)
committerLinus Torvalds <torvalds@linux-foundation.org>
Sun, 12 Jul 2009 18:25:04 +0000 (11:25 -0700)
commita137802ee839ace40079bebde24cfb416f73208a
treedb6e93c3d1c9f5808a2d78fcf91fe96260eb786b
parent8b9f2caa02e96bb92327e3b4557adbb3f1203dc7
Don't use '-fwrapv' compiler option: it's buggy in gcc-4.1.x

This causes kernel images that don't run init to completion with certain
broken gcc versions.

This fixes kernel bugzilla entry:
http://bugzilla.kernel.org/show_bug.cgi?id=13012

I suspect the gcc problem is this:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28230

Fix the problem by using the -fno-strict-overflow flag instead, which
not only does not exist in the known-to-be-broken versions of gcc (it
was introduced later than fwrapv), but seems to be much less disturbing
to gcc too: the difference in the generated code by -fno-strict-overflow
are smaller (compared to using neither flag) than when using -fwrapv.

Reported-by: Barry K. Nathan <barryn@pobox.com>
Pushed-by: Frans Pop <elendil@planet.nl>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: stable@kernel.org
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Makefile