From: Ziemowit Laski <zlaski@apple.com>
To: "Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: Gabriel Dos_Reis <gdosreis@sophia.inria.fr>,
gcc-bugs@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: GCC-3.2.2 bootstrap FAILURE: 1 reduce/reduce conflict in objc-parse.y
Date: Wed, 29 Jan 2003 00:54:00 -0000 [thread overview]
Message-ID: <E16FA4B2-3313-11D7-AF65-000393673036@apple.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0301280715530.6246-100000@kern.srcf.societies.cam.ac.uk>
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
>>> <http://gcc.gnu.org/ml/gcc-bugs/2003-01/msg00900.html>.
>>
>> 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
next prev parent reply other threads:[~2003-01-28 22:57 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 22:18 Gabriel Dos_Reis
2003-01-27 22:32 ` Gabriel Dos Reis
2003-01-27 22:52 ` Paolo Carlini
2003-01-27 23:10 ` Gabriel Dos Reis
2003-01-28 0:03 ` Raja R Harinath
2003-01-28 0:23 ` Gabriel Dos Reis
2003-01-27 22:56 ` Joseph S. Myers
2003-01-27 23:20 ` Gabriel Dos Reis
2003-01-28 1:47 ` Ziemowit Laski
2003-01-28 5:19 ` Gabriel Dos_Reis
2003-01-28 11:39 ` Joseph S. Myers
2003-01-28 12:43 ` Gabriel Dos Reis
2003-01-29 0:54 ` Ziemowit Laski [this message]
2003-01-29 1:32 ` Joseph S. Myers
2003-01-29 1:49 ` Ziemowit Laski
2003-01-29 2:18 ` Joseph S. Myers
2003-01-29 4:09 ` Stan Shebs
2003-01-30 2:01 ` Joe Buck
2003-01-29 6:02 ` Ziemowit Laski
2003-01-30 1:43 ` Joe Buck
2003-01-30 2:07 ` Joseph S. Myers
2003-01-30 3:40 ` Joe Buck
2003-01-30 4:20 ` Ziemowit Laski
2003-01-30 4:27 ` Joseph S. Myers
2003-01-30 6:56 ` Ziemowit Laski
2003-01-30 11:07 ` Neil Booth
2003-01-30 14:04 ` Mark Mitchell
2003-01-30 22:43 ` Neil Booth
2003-01-30 23:59 ` Ziemowit Laski
2003-01-31 13:26 ` Joseph S. Myers
2003-01-31 21:41 ` Ziemowit Laski
2003-01-28 14:04 Paolo Bonzini
2003-01-30 23:38 Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E16FA4B2-3313-11D7-AF65-000393673036@apple.com \
--to=zlaski@apple.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gdosreis@sophia.inria.fr \
--cc=jsm28@cam.ac.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).