From: Bernd Schmidt <bschmidt@redhat.com>
To: David Malcolm <dmalcolm@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: Fix 69650, bogus line numbers from libcpp
Date: Mon, 14 Mar 2016 13:20:00 -0000 [thread overview]
Message-ID: <56E6BAB1.6030804@redhat.com> (raw)
In-Reply-To: <1457734166.5425.43.camel@redhat.com>
On 03/11/2016 11:09 PM, David Malcolm wrote:
>> + cpp_error (pfile, CPP_DL_ERROR,
>> + "file \"%s\" left but not entered", new_file);
> ^^^^^^^^
> Although it looks like you're preserving the existing behavior from
> when this was in linemap_add, shouldn't this be
> ORDINARY_MAP_FILE_NAME (from)
> rather than new_file? (i.e. shouldn't it report the name of the file
> being *left*, rather than the one being entered?)
Hmm, almost but not quite. We don't necessarily know the name of the
file that's being left, if there's just a single #line directive as in
the testcase. I don't think we can reliably get a meaningful filename
other than the in the line directive. So maybe the error message needs
to be changed to something like "file %s unexpectedly reentered"?
> Can we also have a testcase with a non-empty filename? I'm interested
> in seeing what the exact error messages looks like.
# 1 "v.c"
# 1 "t.h" 1
int t;
# 2 "v.c" 2
int b;
t.h:2:12: error: file "b.c" left but not entered
So this shows the line number for the file we think we are in, which is
t.h. Would you accept this with the wording changed as suggested above?
Bernd
next prev parent reply other threads:[~2016-03-14 13:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56E12FFF.6050800@t-online.de>
2016-03-10 8:40 ` Bernd Schmidt
2016-03-11 22:09 ` David Malcolm
2016-03-14 13:20 ` Bernd Schmidt [this message]
2016-03-21 14:58 ` Bernd Schmidt
2016-03-21 20:17 ` David Malcolm
2016-03-22 1:35 ` Bernd Schmidt
2016-03-23 12:58 ` Richard Biener
2016-03-23 13:21 ` Bernd Schmidt
2016-03-23 14:39 ` Richard Biener
2016-03-24 16:21 ` Bernd Schmidt
2016-03-24 21:42 ` Jeff Law
2016-03-25 18:25 ` Jeff Law
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=56E6BAB1.6030804@redhat.com \
--to=bschmidt@redhat.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@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).