🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.ibm.pc.programmer
Article #85

Re: Best C Compiler

#85
From: Joseph H Allen
Date: Tue, 20 Mar 1990 01:36
38 lines
2619 bytes
In article <1990Mar19.175316.16898@Octopus.COM> stever@octopus.UUCP (Steve Resnick ) writes:
>I have Turbo C and MSC Both. In trying to determine which one builds the 
>tighter code, I compiled MicroEMACS 3.10 (Beta) under MSC. I used the maximum
>optimizations on both. MSC Failed with an internal compiler error. Without 
>optimizations, it compiled and linked, but, alas, Emacs would crash. The
>Turbo C compiled version works fine. I have been using it as my editor at work
>for over a year. The Turbo C version was also 10K smaller. I don't know if
>MicroEMACS is really a good benchmark, but it's big and is supported by 
>a variety of compilers on various platforms.

I've had this problem with a different version of pc emacs (the original
gosling emacs).  MSC 5.1 barfed and turbo C worked after some work (it was
originally written for lattice C and MSC 4.0). 

Try Zortech C.  It makes better code than turbo C but does less dangerous
optimizations than MSC does.  The code it makes is very clean - it does just
what you'd expect an optimizing compiler to do.  The only wierdness is the
way it handles postincrement (and this weirdness is not incorrect.. it's just
weird and slightly slower).

Now only if it had pseudoregisters...

Also the Zortech floating point library is better than both turbo C and MSC
because it's reentrant.  Plus tiny model isn't as braindamaged- with zortech
tiny model and small are equivelent except that tiny model is a .COM file.

I find it very humerous that MSC 6.0 now supports tiny model.  I thought
Mircosoft had decided to drop support on .COM files...

My compiler of choice is still turbo C though.  My 8Mhz PC runs just as fast
as MSC (5.1) on a 20Mhz 386.  I only use MSC or Zortech for the final compile
(if I hadn't used any of turbo C's incompatible features).  Plus I usually
don't care very much about the compilers optimizations anyway since I write
critical sections in assembly.

-- 
            "Come on Duke, lets do those crimes" - Debbie
"Yeah... Yeah, lets go get sushi... and not pay" - Duke
Technical Details
Message-ID: <9873@wpi.wpi.edu>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!think!husc6!m2c!wpi!jhallen
References: <1722@geocub.greco-prog.fr> <1264@doitcr.doit.sub.org> <1990Mar19.175316.16898@Octopus.COM>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!think!husc6!m2c!wpi!jhallen
From: jhallen@wpi.wpi.edu (Joseph H Allen)
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Re: Best C Compiler
Keywords: Compilers
Message-ID: <9873@wpi.wpi.edu>
Date: 20 Mar 90 01:36:06 GMT
References: <1722@geocub.greco-prog.fr> <1264@doitcr.doit.sub.org> <1990Mar19.175316.16898@Octopus.COM>
Reply-To: jhallen@wpi.wpi.edu (Joseph H Allen)
Organization: Worcester Polytechnic Institute, Worcester ,MA
Lines: 38