public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: neil@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	ted@arraycomm.com
Subject: Re: preprocessor/7022: #line in .i files is broken in gcc 3.1
Date: Thu, 13 Jun 2002 13:29:00 -0000	[thread overview]
Message-ID: <20020613202930.1472.qmail@sources.redhat.com> (raw)

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


             reply	other threads:[~2002-06-13 20:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-13 13:29 neil [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-13 13:46 Ted Merrill
2002-06-13 13:36 Neil Booth
2002-06-13 12:36 ted

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=20020613202930.1472.qmail@sources.redhat.com \
    --to=neil@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=ted@arraycomm.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).