From: Sam Ravnborg <sam@ravnborg.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: git-commits-head@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Add '-fwrapv' to gcc CFLAGS
Date: Thu, 19 Mar 2009 23:28:48 +0100 [thread overview]
Message-ID: <20090319222848.GA26278@uranus.ravnborg.org> (raw)
In-Reply-To: <200903192159.n2JLx1Bu020711@hera.kernel.org>
On Thu, Mar 19, 2009 at 09:59:01PM +0000, Linux Kernel Mailing List wrote:
> Gitweb: http://git.kernel.org/linus/68df3755e383e6fecf2354a67b08f92f18536594
> Commit: 68df3755e383e6fecf2354a67b08f92f18536594
> Parent: a1e4ee22863d41a6fbb24310d7951836cb6dafe7
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> AuthorDate: Thu Mar 19 11:10:17 2009 -0700
> Committer: Linus Torvalds <torvalds@linux-foundation.org>
> CommitDate: Thu Mar 19 11:10:17 2009 -0700
>
> Add '-fwrapv' to gcc CFLAGS
>
> This makes sure that gcc doesn't try to optimize away wrapping
> arithmetic, which the kernel occasionally uses for overflow testing, ie
> things like
>
> if (ptr + offset < ptr)
>
> which technically is undefined for non-unsigned types. See
>
> http://bugzilla.kernel.org/show_bug.cgi?id=12597
>
> for details.
>
> Not all versions of gcc support it, so we need to make it conditional
> (it looks like it was introduced in gcc-3.4).
>
> Reminded-by: Alan Cox <alan@lxorguk.ukuu.org.uk>
> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
> ---
> Makefile | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index 2e2f4a4..f607658 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -347,6 +347,7 @@ KBUILD_CPPFLAGS := -D__KERNEL__
> KBUILD_CFLAGS := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \
> -fno-strict-aliasing -fno-common \
> -Werror-implicit-function-declaration
> +KBUILD_CFLAGS += $(call cc-option,-fwrapv)
> KBUILD_AFLAGS := -D__ASSEMBLY__
>
> # Read KERNELRELEASE from include/config/kernel.release (if it exists)
Path is buggy.
We have several architectures that plays strange games with $(CC)
and $(CROSS_COMPILE).
So we need to postpone any use of $(call cc-option..)
until we have included the arch specific Makefile so
we try with the correct $(CC) version.
If you move it below the include at around line 530 you
should be safe.
Sam
next parent reply other threads:[~2009-03-19 22:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200903192159.n2JLx1Bu020711@hera.kernel.org>
2009-03-19 22:28 ` Sam Ravnborg [this message]
2009-03-19 22:50 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090319222848.GA26278@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=git-commits-head@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®