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

The following reply was made to PR preprocessor/7022; it has been noted by GNATS.

From: Neil Booth <neil@daikokuya.demon.co.uk>
To: ted@arraycomm.com
Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org
Subject: Re: preprocessor/7022: #line in .i files is broken in gcc 3.1
Date: Thu, 13 Jun 2002 21:31:14 +0100

 ted@arraycomm.com wrote:-
 
 > I think there are two areas in the source code that need a
 > fix.  Most importantly, there is some problem with generic
 > #line handling that i have not figured out.
 > Secondarily, there is code to peek at the first line of a
 > file for a # <number> directive, which is clearly broken
 > since it does not check for #line ... if this never
 > got fixed it would be no big deal.
 
 That code is deliberate too.  Remember that the .i file is
 really just a contract between the preprocessor and the compiler,
 whose semantics and format need not be documented, and do change
 subtly from time to time.
 
 The compiler expects to see a # <NUM> line at the beginning
 of a file to tell it what the original file was.  The preprocessor
 doesn't output #line, so there is no check for it.
 
 Neil.


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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-13 13:36 Neil Booth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-13 13:46 Ted Merrill
2002-06-13 13:29 neil
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=20020613203602.5216.qmail@sources.redhat.com \
    --to=neil@daikokuya.demon.co.uk \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).