From: Adrian Bunk <bunk@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Glauber de Oliveira Costa <gcosta@redhat.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Jeremy Fitzhardinge <jeremy@goop.org>,
glommer@gmail.com
Subject: Re: [PATCH] Wipe out traditional opt from x86_64 Makefile
Date: Thu, 25 Oct 2007 20:30:55 +0200 [thread overview]
Message-ID: <20071025183055.GN30533@stusta.de> (raw)
In-Reply-To: <4720D8EA.1090501@zytor.com>
On Thu, Oct 25, 2007 at 10:56:58AM -0700, H. Peter Anvin wrote:
> Adrian Bunk wrote:
>> On Thu, Oct 25, 2007 at 09:47:52AM -0300, Glauber de Oliveira Costa wrote:
>>> Among other things, using -traditional as a gcc option stops us from
>>> using macro token pasting, which is a feature we heavily rely on.
>>>
>>> There was still a use of -traditional in arch/x86/kernel/Makefile_64,
>>> which this patch removes.
>>>
>>> I don't see any problems building kernels in my x86_64 box without
>>> -traditional.
>>> ...
>> Does it also work with gcc 3.2 ?
>
> It wouldn't be a gcc version issue, it would be a binutils (ld) version
> issue.
Sorry for the dumb question, but how does or did the gcc -traditional
option affect ld?
> -hpa
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-10-25 18:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 12:47 [PATCH] Wipe out traditional opt from x86_64 Makefile Glauber de Oliveira Costa
2007-10-25 16:03 ` Glauber de Oliveira Costa
2007-10-25 17:23 ` H. Peter Anvin
2007-10-25 17:36 ` Adrian Bunk
2007-10-25 17:56 ` H. Peter Anvin
2007-10-25 18:30 ` Adrian Bunk [this message]
2007-10-25 18:35 ` Jeremy Fitzhardinge
2007-10-26 19:47 ` Glauber de Oliveira Costa
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=20071025183055.GN30533@stusta.de \
--to=bunk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=gcosta@redhat.com \
--cc=glommer@gmail.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox