Subject: Re: Making the (asm) world safe for modern cpp
To: Jason Thorpe <firstname.lastname@example.org>
From: Jim Wise <email@example.com>
Date: 09/17/2003 21:19:25
-----BEGIN PGP SIGNED MESSAGE-----
On Wed, 17 Sep 2003, Jason Thorpe wrote:
>On Wednesday, September 17, 2003, at 11:02 AM, Jim Wise wrote:
>> Currently, asm sources which are processed with cpp (.S) files are run
>> through `-traditional-cpp', rather than modern cpp. This should
>> as `-traditional-cpp' will _eventually_ go away, and as it leads to
>> subtle differences in macro expansion between c and assembly source
>No, -traditional-cpp won't go away. It was specifically re-added to
>GCC 3.3's preprocessor because some assembly language syntaxes are
>incompatible with ISO C's preprocessor semantics.
That said, given that using -traditional-cpp for .S assembly source
pre-processing brings in subtle differences in pre-processor syntax
between our c and assembly language source files, is there any reason
_we_ should continue to use -traditional-cpp?
Are there any platforms where gas/gcc do not provide a
modern-cpp-friendly assembly syntax?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)
-----END PGP SIGNATURE-----