gcc really, really slow?

Compiling my applications from 4.25 to RTP I find that gcc seems a lot slower than old Watcom C (like many times slower). Has anyone else noticed this?

“Art Hays” <avhays@nih.gov> wrote in message
news:Voyager.010123135407.5898283A@lsr-tstb.lsrnet.nei.nih.gov

Compiling my applications from 4.25 to RTP I find that gcc seems a lot
slower than old Watcom C (like many times slower). Has anyone else noticed

this?

Yes, nothing is wrong with your system :wink: GCC fpriorities are
portablility and ability to compile for multiple target, not to be fast.

I hear gcc 3.0.0 should be faster.

Mario Charest wrote:

“Art Hays” <> avhays@nih.gov> > wrote in message
news:> Voyager.010123135407.5898283A@lsr-tstb.lsrnet.nei.nih.gov> …
Compiling my applications from 4.25 to RTP I find that gcc seems a lot
slower than old Watcom C (like many times slower). Has anyone else noticed
this?

Yes, nothing is wrong with your system > :wink: > GCC fpriorities are
portablility and ability to compile for multiple target, not to be fast.

I hear gcc 3.0.0 should be faster.

We also have seen this behaviour. We are using the gcc (cross) compiler
on both platforms and the rtp host compiles 3 to 4 times slower and
the qnx 4.25 host if we compiling over the network.

If we place all created files (objects, dependency files and executable)
locally on the rtp machine the compilation speed is increased. But
anyway the qnx 4.25 host is always faster…

Is there probably a problem located in the tcpip stack or network driver
of the rtp stuff?