Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site heurikon.UUCP
Path: utzoo!linus!philabs!seismo!uwvax!heurikon!jeff
From: jeff@heurikon.UUCP
Newsgroups: net.micro.cpm
Subject: Re: DRI C Compiler Woes
Message-ID: <185@heurikon.UUCP>
Date: Fri, 27-Jan-84 03:37:48 EST
Article-I.D.: heurikon.185
Posted: Fri Jan 27 03:37:48 1984
Date-Received: Sat, 28-Jan-84 02:43:58 EST
References: <15918@sri-arpa.UUCP>
Organization: Heurikon Corp., Madison WI
Lines: 20

Your report was on CP/M-86 'C' compiler bugs and DRI's failure
to fix them in the second release.  I don't think DRI concentrates
too much on their compilers.  We were a beta test site for CP/M-68K.
The O/S worked fine, but wow(!) were there ever a lot of 'C' compiler
bugs.  They've acknowledged all of them and pointed out that they
are relying on their supplier to fix them, since they didn't write
the thing.  (I'll tell you who did if you ask, but not on the net.)

There's only been one release of CP/M-68K so far, and I'm waiting
to see if the bugs are fixed in the next release.  But, frankly,
I won't be too surprised it they aren't.

Fortunately, all of the bugs have work-arounds.  But I'm slightly
bald now from pulling hair, and I've gotten very good at reading
the cryptic *.s files produced by the compiler to find out what
the 68K is *really* doing.
-- 
/"""\	Jeffrey Mattox, Heurikon Corp, Madison, WI
|O.O|	{harpo, hao, philabs}!seismo!uwvax!heurikon!jeff  (news & mail)
\_=_/				     ihnp4!heurikon!jeff  (mail)