Re: c++/10603: [3.4 regression] [new parser] failing to print problematic token upon parse error

Re: c++/10603: [3.4 regression] [new parser] failing to print problematic token upon parse error

[Giovanni Bajo]

The following reply was made to PR c++/10603; it has been noted by GNATS.

From: "Giovanni Bajo" <giovannibajo@libero.it>
To: "Gerald Pfeifer" <pfeifer@dbai.tuwien.ac.at>,
	<gcc-gnats@gcc.gnu.org>,
	<gcc-bugs@gcc.gnu.org>,
	<nobody@gcc.gnu.org>,
	<gcc-prs@gcc.gnu.org>
Cc:  
Subject: Re: c++/10603: [3.4 regression] [new parser] failing to print problematic token upon parse error
Date: Fri, 2 May 2003 16:28:12 +0200

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10603
 
 Let me add that this is not restricted to this very specific case. The new
 parser surely needs work in error reporting, because I could post endless
 regressions I found on this regard.
 
 Giovanni Bajo
 

Re: c++/10603: [3.4 regression] [new parser] failing to print problematic token upon parse error

[gerald]

Synopsis: [3.4 regression] [new parser] failing to print problematic token upon parse error

State-Changed-From-To: open->analyzed
State-Changed-By: gerald
State-Changed-When: Fri May  2 14:08:19 2003
State-Changed-Why:
    Confirmed.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10603

c++/10603: [3.4 regression] [new parser] failing to print problematic token upon parse error

[pfeifer]

>Number:         10603
>Category:       c++
>Synopsis:       [3.4 regression] [new parser] failing to print problematic token upon parse error
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Fri May 02 14:06:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     pfeifer@dbai.tuwien.ac.at
>Release:        unknown-1.0
>Organization:
>Environment:
gcc version 3.4 20030502 (experimental)
>Description:
Our diagnoses for the following piece of code
used to be

  int f(int not) {
    return 1-not;
  } 

rather confusing, but now the source of the problem really
is very hard to see:

  x.cc:1: error: expected primary-expression
  x.cc:1: error: expected `,' or `;'

(Hint: the problem is that "not" is parsed as "!".)
>How-To-Repeat:
  % /sw/gcc-3.2.2/bin/g++ x.cc
  x.cc:1: parse error before `!' token
  x.cc: In function `int f(...)':
  x.cc:2: parse error before `;' token

  % gccvs x.cc
  x.cc:1: error: expected primary-expression
  x.cc:1: error: expected `,' or `;'
>Fix:
Also provide the token that lead to the parse error, so that
the user can see the actual problem.
>Release-Note:
>Audit-Trail:
>Unformatted: