Bug 512652 - kernel: use -fno-strict-overflow instead of -fwrapv [rhel-4.9]
kernel: use -fno-strict-overflow instead of -fwrapv [rhel-4.9]
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
All Linux
high Severity high
: rc
: ---
Assigned To: Red Hat Kernel Manager
Red Hat Kernel QE team
Depends On: 512650
  Show dependency treegraph
Reported: 2009-07-20 03:52 EDT by Eugene Teo (Security Response)
Modified: 2013-01-10 21:32 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 512650
Last Closed: 2009-07-29 04:10:27 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Eugene Teo (Security Response) 2009-07-20 03:52:54 EDT
+++ This bug was initially created as a clone of Bug #512650 +++

Description of problem:
[PATCH] 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:

I suspect the gcc problem is this:

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.

Upstream commit:

--- Additional comment from eteo@redhat.com on 2009-07-20 03:49:08 EDT ---

Related to bug 491267.

Note You need to log in before you can comment on or make changes to this bug.