From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5231 invoked by alias); 28 Jan 2003 22:57:22 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 5213 invoked from network); 28 Jan 2003 22:57:21 -0000 Received: from unknown (HELO mail-out1.apple.com) (17.254.0.52) by 172.16.49.205 with SMTP; 28 Jan 2003 22:57:21 -0000 Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out1.apple.com (8.11.3/8.11.3) with ESMTP id h0SMvKw22007; Tue, 28 Jan 2003 14:57:20 -0800 (PST) Received: from scv3.apple.com (scv3.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Tue, 28 Jan 2003 14:57:19 -0800 Received: from apple.com (polskifiat.apple.com [17.201.24.57]) by scv3.apple.com (8.11.3/8.11.3) with ESMTP id h0SMvJf25902; Tue, 28 Jan 2003 14:57:19 -0800 (PST) Date: Wed, 29 Jan 2003 00:54:00 -0000 Subject: Re: GCC-3.2.2 bootstrap FAILURE: 1 reduce/reduce conflict in objc-parse.y Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) Cc: Gabriel Dos_Reis , gcc-bugs@gcc.gnu.org, gcc@gcc.gnu.org To: "Joseph S. Myers" From: Ziemowit Laski In-Reply-To: Message-Id: Content-Transfer-Encoding: 7bit X-SW-Source: 2003-01/txt/msg01515.txt.bz2 On Monday, Jan 27, 2003, at 23:16 US/Pacific, Joseph S. Myers wrote: > On Mon, 27 Jan 2003, Ziemowit Laski wrote: > >>> An objc maintainer needs to review >>> . >> >> I'm not the maintainer, but the patch is wrong. One cannot replace >> 'protocolrefs' with 'non_empty_protocolrefs', as they are optional. > > A reduce/reduce conflict is still a bug, even if the fix is more > complicated. Removing %expect is only a workaround. A reduce/reduce conflict is certainly an annoyance, but it is not a bug -- bison has a deterministic, POSIX-annointed method for dealing with it, which the grammar writer knows and expects. A slightly better way, IMHO, would be to allow %expect to take an optional second argument %expect sr_conflicts [, rr_conflicts] so that the grammar writer could state her intent more clearly. However, since this mechanism doesn't exist, whacking the %expect altogether is a sensible approach. --Zem -------------------------------------------------------------- Ziemowit Laski 1 Infinite Loop, MS 301-2K Mac OS X Compiler Group Cupertino, CA USA 95014-2083 Apple Computer, Inc. +1.408.974.6229 Fax .5477