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: GCC-3.2.2 bootstrap FAILURE: 1 reduce/reduce conflict in objc-parse.y

From: Ziemowit Laski <zlaski at apple dot com>
To: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
Cc: Ziemowit Laski <zlaski at apple dot com>, Mark Mitchell <mark at codesourcery dot com>, "gcc-bugs at gcc dot gnu dot org" <gcc-bugs at gcc dot gnu dot org>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
Date: Fri, 31 Jan 2003 12:43:33 -0800
Subject: Re: GCC-3.2.2 bootstrap FAILURE: 1 reduce/reduce conflict in objc-parse.y

On Friday, Jan 31, 2003, at 02:44 US/Pacific, Joseph S. Myers wrote:

On Thu, 30 Jan 2003, Ziemowit Laski wrote:
I looked back over the thread and I agree with you and with your
reasoning. Unfortunately, I don't think I have a leg to stand on in
arguing this case, since I don't know if/when my employer would
allocate the resources needed for me or others to do this work. :-(
You do not need large time allocations to do incremental development as I
proposed. You can unify one function at a time between front ends with a
fairly small amount of time for each function, and every such merge has an
immediate benefit.

You are absolutely right in principle; however, even an incremental effort
on our (i.e., Apple's) part would require a diversion of resources which
may not be forthcoming.

--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

References:
- Re: GCC-3.2.2 bootstrap FAILURE: 1 reduce/reduce conflict inobjc-parse.y
  - From: Joseph S. Myers

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