DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=V02LYGZW7b+jTEMa3cmCNFqv6u/ePGDi3cApdMvWnA5qIGpbg5NRrWHbXbl7o6OvDTzW1GpjLFWqgldZZIP0Dlkdfv1dHtbg9FS5IXeAqP6ANqYVauzLQYNQ2uIXnjwQ7hQKFnM3nuducURfwXpNbJlY27ovziLzerKQJHu186w=
Message-ID: <5d6222a80710242016p27be8bcdk23421efb5990e14a@mail.gmail.com>
Date: Thu, 25 Oct 2007 01:16:24 -0200
From: "Glauber de Oliveira Costa" <glommer@gmail.com>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
       "Jeremy Fitzhardinge" <jeremy@goop.org>
Subject: Using -traditional in EXTRA_AFLAGS
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1128
Lines: 30

Guys,

is there any particular reason we're using -traditional in
EXTRA_AFLAGS in Makefiles?

According to
http://gcc.gnu.org/onlinedocs/cpp/Traditional-macros.html#Traditional-macros,
(and to my painful recent experience), it disallows the use of token
pasting in pre-processor macros, which is a functionality we heavily
rely upon for the rest of kernel things.

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?
-- 
Glauber de Oliveira Costa.
"Free as in Freedom"
http://glommer.net

"The less confident you are, the more serious you have to act."
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/