Re: gprof call counts wrong in multithreaded program

2010-06-08 Thread Nick Clifton
Hi Kalle, It is an improvement, but I think it would be even better to specifically mention glibc. Ok - I have checked in a patch to change the paragraph to read as follows: By contrast, the number-of-calls and basic-block figures are derived by counting, not sampling. They are completel

Re: gprof call counts wrong in multithreaded program

2010-05-30 Thread Kalle Olavi Niemitalo
Hi, Nick. You write: > How do you feel about the attached patch to update the documentation ? It is an improvement, but I think it would be even better to specifically mention glibc. Usually, I expect GNU programs to work best with glibc and GCC; if you just warn that the counting function migh

Re: gprof call counts wrong in multithreaded program

2010-05-26 Thread Nick Clifton
Hi Kalle, [I am very sorry about taking so long to reply to your email]. "By contrast, the number-of-calls and basic-block figures are derived by counting, not sampling. They are completely accurate and will not vary from run to run if your program is deterministic." In one series of three 9

gprof call counts wrong in multithreaded program

2010-05-13 Thread Kalle Olavi Niemitalo
Dear binutils maintainers, I was recently profiling some algorithm improvements in the Bos Wars game, using gcc -pg and gprof on amd64. To my surprise, when I ran the same input through the game several times, gprof displayed different timings _and_ call counts each time, even though section 6.1