This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC-3.2.2 bootstrap FAILURE: 1 reduce/reduce conflict inobjc-parse.y
- From: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- To: Ziemowit Laski <zlaski at apple dot com>
- Cc: 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 10:44:55 +0000 (GMT)
- Subject: Re: GCC-3.2.2 bootstrap FAILURE: 1 reduce/reduce conflict inobjc-parse.y
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.
The toplevel autoconfiscation is an excellent example of how large
changes, which overall achieve a substantial reorganisation, can and
should be done incrementally.
--
Joseph S. Myers
jsm28@cam.ac.uk