From: Adrian Bunk <bunk@kernel.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Andi Kleen <ak@suse.de>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: unify x86 Makefile(s)
Date: Sat, 29 Dec 2007 11:52:53 +0200 [thread overview]
Message-ID: <20071229095253.GC27360@does.not.exist> (raw)
In-Reply-To: <20071229093904.GA17390@uranus.ravnborg.org>
On Sat, Dec 29, 2007 at 10:39:04AM +0100, Sam Ravnborg wrote:
> On Sat, Dec 29, 2007 at 12:13:24AM +0200, Adrian Bunk wrote:
> > On Fri, Dec 28, 2007 at 10:23:41PM +0100, Sam Ravnborg wrote:
> > >...
> > > Noteworthy remarks on the unification:
> > >...
> > > - -funit-at-a-time should be easy to unify but it looks like we have a bug
> > > in 32 bit. We only enable -funit-at-a-time for gcc less than 0400 if they
> > > support it
> >
> > No, we _dis_able it on 32bit if a gcc < 4.0 supports it.
> I have:
> $ gcc --version
> gcc (GCC) 4.1.2 20070925 (Red Hat 4.1.2-33)
>
> And with the current code in arch/x86/Makefile_32 I do not
> have -funit-at-a-time.
>...
You do not have this option, but you do not need it since it's enabled
with -O in all gcc versions that support it except for some vendor
backports to gcc 3.3.
>...
> This is the relevant snippet from the Makefile:
> KBUILD_CFLAGS += $(shell if [ $(call cc-version) -lt 0400 ] ; then echo $(call cc-option,-fno-unit-at-a-time); fi ;)
>
> It reads:
> If gcc version is less than 4.00 then enable -funit-at-a-time only for gcc that supports it.
> -funit-at-a-time is NOT enabled for gcc >= 4.00
It is not _explicitely_ enabled for gcc >= 4.0 since it's anyway enabled.
> So it will enable -funit-at-a-time for gcc 3.4 as it is now.
> Which was what we wanted to avoid..
> So I see no reason not to enable it uncondintionally (if gcc supports it) as we have
> used it for 3.4 for as long as we have introduced -funit-at-a-time.
We have never used it with gcc 3.4 on i386.
> Sam
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-12-29 9:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-28 21:23 [PATCH] x86: unify x86 Makefile(s) Sam Ravnborg
2007-12-28 22:13 ` Adrian Bunk
2007-12-29 2:14 ` Andi Kleen
2007-12-29 8:07 ` Adrian Bunk
2007-12-29 9:39 ` Sam Ravnborg
2007-12-29 9:52 ` Adrian Bunk [this message]
2007-12-29 12:16 ` Andi Kleen
2007-12-29 12:54 ` Adrian Bunk
2007-12-29 18:22 ` Sam Ravnborg
2007-12-29 18:24 ` Andi Kleen
2007-12-29 18:58 ` Sam Ravnborg
2007-12-29 21:17 ` Andi Kleen
2007-12-29 21:45 ` Adrian Bunk
2007-12-30 2:00 ` Andi Kleen
2007-12-30 11:01 ` Adrian Bunk
2007-12-29 2:22 ` Andi Kleen
2007-12-29 8:07 ` Sam Ravnborg
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=20071229095253.GC27360@does.not.exist \
--to=bunk@kernel.org \
--cc=ak@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
/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.