bad performance of g77(egcs) on Linux/Alpha

Michal Jaegermann michal@ellpspace.math.ualberta.ca
Thu Apr 9 22:42:00 GMT 1998


> 
> Well, the age-old way to determine this is to run the code on  
> different architectures compiled with -pg and looking at the gprof  
> output to see where it's spending its time.

There are assorted problems with profiling on Linux/Alpha
and, frankly speaking, I somewhat hoped that somebody may have
already a handle on the problem already. :-)

> Unfortunately, you forgot to include the necessary input file, so I  
> can't do this experiment on my own m68k-next-nextstep3 system.

Ooops, Toon, you are right.   Sorry!  Sending reports late at night
has distinct disadvantages. Here it is in the full glory.
Feed it from stdin.  There is quite a few lines of output on stdout
and sending them to /dev/null can be a good idea.

-------------------------------cut here--------------------------------
74,183.85
0.02
19.3
800 1.
-10. -10.
-------------------------------cut here--------------------------------

  Michal




More information about the Gcc-bugs mailing list