Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!AI.MIT.EDU!rms
From: rms@AI.MIT.EDU
Newsgroups: gnu.gcc
Subject: Reliability
Message-ID: <8906180413.AA02301@sugar-bombs.ai.mit.edu>
Date: 18 Jun 89 04:13:07 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 18

A few people have pointed out their serious disappointment with the
number of bugs remaining in GCC.  This has convinced me that I have
to do more than I have been doing to strive for reliability.

Already I have been doing longer periods of pre-tests before each
release, with more pre-testers.  But this doesn't seem to be enough.

So I am considering separating off GCC version 1, which would be
maintained for bug fixes only, from a new version 2, in which the new
features such as instruction scheduling and so on would be added.
This would probably mean a considerable delay in getting those
features into distribution, but that might be worthwhile if version 1
becomes more solid.  The final merge with G++ would also be put off
for version 2.

Meanwhile, I very much need the help of someone who understands the
X server well enough to find the compilation error if GCC should fail
to compile it properly.