🚀 go-pugleaf

I can strongly recommend GCC and G++ for the Sun. I use them as production
compilers, though they are officially still in beta test.  Both have bugs
remaining that show up in the most demanding applications; however, I tend
to write reasonably well-structured code with modest size modules, and I
haven't seen a compiler bug from either compiler in several versions. GCC
is a portable, retargetable, highly optimizing C compiler. It supports
both old-style C (if you specify '-traditional' it accepts almost
identically the same language as Reiser's cpp + Johnson's pcc) and X3J11
DP-ANS C. With all the optional warnings turned on I find it more
effective at preening code for validity than lint. Inclusion of
information for debugging (-g) doesn't conflict with optimization (-O),
unlike pcc (though single-stepping through optimized code is sometimes
amusing; variables which have been optimized out of existance can't have
their values displayed, sometimes code flow hops about somewhat
disconcertingly due to code rearrangement). Since I am relatively
unconcerned with executable size, I install all programs compiled with '-O
-g'. That make core dumps debuggable, and I can reach out and attach to
running programs if they get wedged (though that sort of problem is not
happening at all frequently, between ANSI function prototype checking and
the other consistency checks that GCC performs at compile time, and the
run-time checking that my libbent performs on library and system calls).

GCC can be FTP-ed from prep.ai.mit.edu, as well as uunet.uu.net and
tut.cis.ohio-state.edu. Tut also has an open UUCP server.

-Bennett
bet@orion.mc.duke.edu