All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: [PATCH,v2] Only add '-fwrapv' to gcc CFLAGS for gcc 4.2 and later
Date: Thu, 23 Jul 2009 16:27:16 +0200	[thread overview]
Message-ID: <20090723142716.GA9233@merkur.ravnborg.org> (raw)
In-Reply-To: <200907231446.44929.elendil@planet.nl>

On Thu, Jul 23, 2009 at 02:46:44PM +0200, Frans Pop wrote:
> On Saturday 18 July 2009, Sam Ravnborg wrote:
> > > I based my patch on arch/x86/Makefile:
> > > 35:        KBUILD_CFLAGS += $(shell if [ $(call cc-version) -lt 0400 ] ; then \
> > > 36:                echo $(call cc-option,-fno-unit-at-a-time); fi ;)
> > >
> > > Guess that could be improved to use cc-ifversion then.
> >
> > Yes, please...
> 
> I've got patches for x86, ia64, powerpc and um, but have a couple of
> questions before I submit them.
> 
> Can the patches go through your kbuild tree or should they go through the
> arch trees (they will be CCed of course)?
Preferably the arch tress, but I will take what they do not apply.

> 
> In my patches I've left the cc-option check where it existed, so for x86
> you get (tested to work):
> -        KBUILD_CFLAGS += $(shell if [ $(call cc-version) -lt 0400 ] ; then \
> -                echo $(call cc-option,-fno-unit-at-a-time); fi ;)
> +        KBUILD_CFLAGS += $(call cc-ifversion, -lt, 0400, \
> +                               $(call cc-option,-fno-unit-at-a-time))
> 
> Or is it safe to simplify that to just:
> +        KBUILD_CFLAGS += $(call cc-ifversion, -lt, 0400, -fno-unit-at-a-time)
> ?
I think not. The latter would require all gcc versions > 4.00 to support that,
option and looking at the oroginal code it does not.
> 
> > > And a quick git grep gives a few other potential candidates:
> > > arch/parisc/Makefile:129:       @if test "$(call cc-version)" -lt "0303"; then \
> 
> I left this one unchanged as it does not add a compiler option; instead it
> displays an "unsupported' message.
Yes - this is something different.

[I'm away for a few days - will check up on your patches when I'm back].

	Sam

      reply	other threads:[~2009-07-23 14:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-10  7:28 [Bug 13012] 2.6.28.9 causes init to segfault on Debian etch; 2.6.28.8 OK Frans Pop
2009-07-10 14:59 ` Frans Pop
2009-07-12 17:58   ` Linus Torvalds
2009-07-12 17:58     ` Linus Torvalds
2009-07-12 18:24     ` Linus Torvalds
2009-07-13  5:29     ` Ian Lance Taylor
2009-07-25  3:23       ` Dave Jones
2009-07-25 16:49         ` Linus Torvalds
2009-07-10 20:05 ` [PATCH,v2] Only add '-fwrapv' to gcc CFLAGS for gcc 4.2 and later Frans Pop
2009-07-17 22:18   ` Sam Ravnborg
2009-07-17 22:43     ` Frans Pop
2009-07-18  6:59       ` Sam Ravnborg
2009-07-23 12:46         ` Frans Pop
2009-07-23 14:27           ` Sam Ravnborg [this message]

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=20090723142716.GA9233@merkur.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=elendil@planet.nl \
    --cc=linux-kbuild@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.