From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Glauber de Oliveira Costa <glommer@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Using -traditional in EXTRA_AFLAGS
Date: Thu, 25 Oct 2007 08:17:23 -0700 [thread overview]
Message-ID: <4720B383.40701@goop.org> (raw)
In-Reply-To: <5d6222a80710242016p27be8bcdk23421efb5990e14a@mail.gmail.com>
Glauber de Oliveira Costa wrote:
> Guys,
>
> is there any particular reason we're using -traditional in
> EXTRA_AFLAGS in Makefiles?
>
What? Where? I thought I removed them all. Or is this from the x86_64
tree?
> I'd suggest just removing it, but obviously, there might well be
> people with good reasons for it to stay (The same effect of token
> pasting can be achieved in some ways, so if -traditional stays, that's
> not the greatest problem in the world... just that token pasting in
> asm files will diverge from the way in which we (-)traditionally do
> ;-) )
>
> So, does any one have a word on that?
>
Kill -traditional where ever it may be. You might need to fix up some
cruft in the process, but shouldn't be too hard.
J
next prev parent reply other threads:[~2007-10-25 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 3:16 Using -traditional in EXTRA_AFLAGS Glauber de Oliveira Costa
2007-10-25 15:17 ` Jeremy Fitzhardinge [this message]
2007-10-25 15:21 ` Glauber de Oliveira Costa
2007-10-25 18:55 ` Denys Vlasenko
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=4720B383.40701@goop.org \
--to=jeremy@goop.org \
--cc=glommer@gmail.com \
--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