[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gnugo-devel] weird performance problem
From: |
Arend Bayer |
Subject: |
Re: [gnugo-devel] weird performance problem |
Date: |
Fri, 16 Apr 2004 21:51:05 +0200 (CEST) |
> > 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
- [gnugo-devel] weird performance problem, Arend Bayer, 2004/04/16
- Re: [gnugo-devel] weird performance problem, Paul Pogonyshev, 2004/04/16
- Re: [gnugo-devel] weird performance problem, Arend Bayer, 2004/04/16
- Re: [gnugo-devel] weird performance problem, Paul Pogonyshev, 2004/04/16
- Re: [gnugo-devel] weird performance problem,
Arend Bayer <=
- Re: [gnugo-devel] weird performance problem, Paul Pogonyshev, 2004/04/16
- Re: [gnugo-devel] weird performance problem, Arend Bayer, 2004/04/16
- Re: [gnugo-devel] weird performance problem, Paul Pogonyshev, 2004/04/16
- [gnugo-devel] oprofile, Arend Bayer, 2004/04/18
- Re: [gnugo-devel] oprofile, Gunnar Farneback, 2004/04/18
- Re: [gnugo-devel] oprofile, Evan Daniel, 2004/04/18
- Re: [gnugo-devel] oprofile, Arend Bayer, 2004/04/20