🚀 go-pugleaf

Philip Brown wrote:

> On Fri, 14 Mar 2003 04:49:41 -0500, fma@doe.carleton.ca wrote:
> >Markus Gyger wrote:
> >> You might want to take a look at gcc2c and use it with the current
> >> (production) Sun C compiler for maximum speed optimization:
> >>...
> >
> >Actually, I want to stick with gcc because I want transparency
> >between solaris8 and Win2K/Cygwin.
>
> you should have no problems using forte for solaris 8 and gcc on cygwin.
>
> It's easy taking source code developed under forte CC, and recompiling with
> g++. Usually, (almost always) there's nothing extra to do.
> The problem is when you try to go the other way.
>
> --
>   http://www.blastwave.org/ for solaris pre-packaged binaries with pkg-get
>     Organized by the author of pkg-get
> [Trim the no-bots from my address to reply to me by email!]
>          S.1618 http://thomas.loc.gov/cgi-bin/bdquery/z?d105:SN01618:@@@D
>                             http://www.spamlaws.com/state/ca1.html

I do recall years ago when I last used C++, I was in fact making
minor mods to enable compiling with gcc on the suns and HP's CC.
That was on HPUX.  For now, I just want to understand what
coding practices affect speed, in principle, and worry about tweaking
based on compilers/platform later.  I may decide to forgo some of
those for cross-platform portablility e.g. if it involves time to tweak
stuff everytime I migrate from cygwin gcc to solaris forte, I may decide
just to stick with gcc because of its ubiquity.

By the way, gcc has a handy --version switch, but cc on the sun
doesn't.  Is there a way to check beyond any doubt what compiler
it is?

Fred