Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!godot!harvard!seismo!brl-tgr!gwyn
From: gwyn@brl-tgr.ARPA (Doug Gwyn <gwyn>)
Newsgroups: net.lang.c
Subject: Re: PCC bugs
Message-ID: <5568@brl-tgr.ARPA>
Date: Thu, 1-Nov-84 23:23:11 EST
Article-I.D.: brl-tgr.5568
Posted: Thu Nov  1 23:23:11 1984
Date-Received: Sat, 3-Nov-84 07:58:51 EST
References: <4141@tekecs.UUCP>
Organization: Ballistic Research Lab
Lines: 15

> What I would ask is that we forget about this type of "contest" and
> concentrate on finding and fixing bugs. I applaud Don's activities on the
> f77 compiler and would be more than happy to see him set up something
> similar to it for pcc. I would like to see all types of bugs reported,
> not just "core dumpers".

Right, let's try to fix PCC bugs.  It would be a pity to start with the
UNIX/32V or USG 3.0 PCC (whatever it is that 4.2BSD comes with), since
I have found that later releases of PCC have had major portions
rewritten to fix bugs.  Starting with the latest release would seem to
be the most productive approach.

Speaking of which, can anyone predict whether PCC2 is going to supplant
PCC in the near future?  Last I heard, it was considerably slower than
PCC so maybe PCC will be around for a while.