Re: [gnugo-devel] weird performance problem

[Arend Bayer]

> > Still, I got only <15% of CPU time for a gnugo that I had explicitly
> > compiled with -pg and -lc_p.
> 
> I don't understand.  Do you mean the profiler eats 85% of CPU time?

Sorry, I meant libc got less than 15% CPU time.

> And what is the `c_p' library?  The profiler library?

c_p is the glibc compiled with -pg, usually available in a package called
'glibc-profile'. Linking against that instead of standard glibc means
that the C library calls made by gnugo will be included in the gprof
output.

Arend