This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: c/8927: Gcc give error for wrong line of C code.


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



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]