public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aaron.hill at wdc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/101968] Preprocessor line number statements become wrong after '#include'
Date: Wed, 18 Aug 2021 20:23:18 +0000	[thread overview]
Message-ID: <bug-101968-4-rABQWrqIWQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101968-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101968

--- Comment #1 from Aaron Hill <aaron.hill at wdc dot com> ---
Created attachment 51321
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51321&action=edit
Add the empty 'foo.h' file used by 'test.cpp'

This file contains a blank line, to allow me to attach it to this issue.
However, the issue can also be reproduced with a completely empty file named
'foo.h'

      reply	other threads:[~2021-08-18 20:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18 20:21 [Bug preprocessor/101968] New: " aaron.hill at wdc dot com
2021-08-18 20:23 ` aaron.hill at wdc dot com [this message]

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=bug-101968-4-rABQWrqIWQ@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).