🚀 go-pugleaf

Markus Gyger wrote:

> Fred Ma <fma@doe.carleton.ca> writes:
> > 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:
> > >
> > > http://soldc.sun.com/migration/linux/gcc2c_tool.html
> > > http://access1.sun.com/s1sprod/
> >
> > Actually, I want to stick with gcc because I want transparency
> > between solaris8 and Win2K/Cygwin.
>
> gcc2c is just a patch for gcc's backend so that it produces
> ISO C code that is then fed to another optimizing C compiler.
> Kind of like the early C++ compilers/translators worked (cfront).
>
> Markus

Hi, Markus,

I took a look at the description.  It looks interesting.
Natural question is why not just use sun's CC directly
when compiling on solaris?

There is another factor that I have to consider.  That
is the fact you have to modify the build of gcc.  It took
about a week to learn enough to try (four
times) to build my own gcc (I am nonadministrator).
This included all the facilities required to test it.  It never
passed the tests without many errors, different errors
each time.  Since I couldn't tell which ones were important,
I didn't install it; my concern was that I couldn't tell which
files to remove in order to uninstall everything.  In the end
I asked my sysadmin to install premade binaries for solaris.
So building gcc is a bit of a problem.

As soon as I finish recoding for matlab, I can do a speed
comparison to confirm that compiling with PIC and as shared
does not adversely affect executio speed.  30% speed
increase from using gcc2c is somewhat significant, and
I'll see if in the future, time permits me to ramp up on what's
necessary to make it work.  Thanks for the suggestion.

Fred