This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: preprocessor/7022: #line in .i files is broken in gcc 3.1
- From: Ted Merrill <ted at arraycomm dot com>
- To: neil at gcc dot gnu dot org, <gcc-bugs at gcc dot gnu dot org>, <gcc-prs at gcc dot gnu dot org>,<nobody at gcc dot gnu dot org>, <ted at arraycomm dot com>, <gcc-gnats at gcc dot gnu dot org>
- Date: Thu, 13 Jun 2002 13:42:59 -0700 (PDT)
- Subject: Re: preprocessor/7022: #line in .i files is broken in gcc 3.1
You are basically saying that the only preprocessor you will support
is the one shipped with GCC.
While that is "legally" ok from the point of the C standard,
it is a very restrictive view.
However, i suppose you have more important things to worry about,
and i will (have, in fact) changed the tool we use.
Thanks for considering this issue,
Ted Merrill
On 13 Jun 2002 neil@gcc.gnu.org wrote:
> Synopsis: #line in .i files is broken in gcc 3.1
>
> State-Changed-From-To: open->closed
> State-Changed-By: neil
> State-Changed-When: Thu Jun 13 13:29:29 2002
> State-Changed-Why:
> This is intentional: -fpreprocessed only expects to see what can appear in a preprocessed file. In particular, it doesn't expand macros, and #line expects macros to expand.
>
> Please change your tool to do the # markers; they work on all versions of GCC.
>
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7022
>