This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: c/8927: Gcc give error for wrong line of C code.
- From: Steven Bosscher <s dot bosscher at student dot tudelft dot nl>
- To: nobody at gcc dot gnu dot org
- Cc: gcc-prs at gcc dot gnu dot org,
- Date: 15 Feb 2003 22:06:00 -0000
- Subject: Re: c/8927: Gcc give error for wrong line of C code.
- Reply-to: Steven Bosscher <s dot bosscher at student dot tudelft dot nl>
The following reply was made to PR c/8927; it has been noted by GNATS.
From: Steven Bosscher <s.bosscher@student.tudelft.nl>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gp@qnx.com,
nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org
Cc: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
Subject: Re: c/8927: Gcc give error for wrong line of C code.
Date: 15 Feb 2003 22:56:46 +0100
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8927
The same problem happens for g++, so this is not a C bug.
c_lex() and c-parse.in:_yylex() return the right line number for the
token. But bison looks ahead a bit and that causes the line number to
advance as well. This is also why saving the line number in the
"primary" production doesn't help: Before we parse primary:IDENTIFIER,
we've already advanced the line number.
So my guess is that this is a cpplib bug: It should not advance the line
number until the previous token is accepted. Dunno how to attack this
bug.
Greetz
Steven