C compilers for A/UX

[Jim Jagielski]

In article <1990Sep10.002711.22219 at servalan.uucp> rmtodd at servalan.uucp (Richard Todd) writes:
>jim at jagmac2.gsfc.nasa.gov (Jim Jagielski) writes:
>
>>I have the Unisoft Optimizing C Compiler for A/UX (GreenHills), A/UX cc
>>and GnuC 1.37.91. Without a doubt, the Unisoft compiler makes tight, fast
>>code. cc isn't very fast or tight, but very stable. And it supports shared
>>libraries (Unisoft doesn't... see below). But I've had NOTHING but bad luck
>>using GnuC (gcc)!! Weird behavior, core dumps, crashes, bombs, etc...
>
>  *** misc stuff about  things Richard has successfully compiled ***
>--

Since my posting, I have recieved a LOT of mail about problems that others have
had with gcc 1.37.91 (not only A/UX version, but others). What version are you
using and running... that may be the problem too.

Then again, who knows? I'll try gcc a few more times, but considering that
it's behavior is not the same as cc, I may still drop it. After all, how
can you make sure that every little flag that you need is set, until the
program craps out on you? And then, how can you tell which one...

Considering that most app's are written and compiled using cc (since it's 
included with most platforms), cc may still be a "safe" bet...
--
=======================================================================
#include <std/disclaimer.h>
                                 =:^)
           Jim Jagielski                    NASA/GSFC, Code 711.1
     jim at jagmac2.gsfc.nasa.gov               Greenbelt, MD 20771

"Kilimanjaro is a pretty tricky climb. Most of it's up, until you reach
 the very, very top, and then it tends to slope away rather sharply."