objc/9267: bison 1.875 doesn't like reduce/reduce errors with %expect N

objc/9267: bison 1.875 doesn't like reduce/reduce errors with %expect N

[harinath]

>Number:         9267
>Category:       objc
>Synopsis:       bison 1.875 doesn't like reduce/reduce errors with %expect N
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Jan 10 15:16:00 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     harinath@cs.umn.edu
>Release:        gcc-3.4
>Organization:
>Environment:
i686-pc-linux-gnu
bison 1.875
>Description:
bison 1.875 exits on compiling objc-parse.y complaining that there are reduce/reduce conflicts where none were expected.

This is a recent change, but it is an extension of the behaviour documented in the Bison 1.28 info documentation.  According to the Bison 1.28 documentation, 

     %expect N

   Here N is a decimal integer.  The declaration says there 
   should be no warning if there are N shift/reduce 
   conflicts and no reduce/reduce conflicts.  The usual 
   warning is given if there are either more or fewer 
   conflicts, or if there are any reduce/reduce conflicts.

Bison 1.875 has converted the warning to an error in those exceptional cirumstances.

%expect was misused in objc-parse.y.  Removing it should not result in more warnings than already there, and also prevents errors when using a newer bison.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:

Re: objc/9267: bison 1.875 doesn't like reduce/reduce errors with %expect N

[gdr]

Synopsis: bison 1.875 doesn't like reduce/reduce errors with %expect N

State-Changed-From-To: open->closed
State-Changed-By: gdr
State-Changed-When: Tue Jan 28 02:00:21 2003
State-Changed-Why:
    Applied suggested patch on 3.2.2, 3.3 and 3.4 (mainline).

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