Path: utzoo!attcan!uunet!lll-winken!elroy.jpl.nasa.gov!jato!mars!kaleb
From: kaleb@mars.jpl.nasa.gov (Kaleb Keithley)
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Re: Best C Compiler
Keywords: Compilers
Message-ID: <3130@jato.Jpl.Nasa.Gov>
Date: 19 Mar 90 19:40:49 GMT
References: <1990Mar19.175316.16898@Octopus.COM>
Sender: news@jato.Jpl.Nasa.Gov
Reply-To: kaleb@mars.UUCP (Kaleb Keithley)
Organization: Jet Propulsion Laboratory, Pasadena, CA.
Lines: 22

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.
>
>BTW - I used TC 2.0 and MSC 5.1
>

I can't imagine what you did, I compiled 3.10 with MSC 5.1, no internal errors,
it created an 88102 byte executable that doesn't crash at all.  It even uses my 
mouse. 
kaleb@mars.jpl.nasa.gov            Jet Propeller Labs
Kaleb Keithley

spelling and grammar flames > /dev/null