This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Are we fast yet?

From: Dimitrios Apostolou <jimis at gmx dot net>
To: Sergei Trofimovich <slyfox at inbox dot ru>
Cc: gcc at gcc dot gnu dot org, Andrey Belevantsev <abel at ispras dot ru>
Date: Mon, 2 Jul 2012 08:11:44 +0300 (EEST)
Subject: Re: Are we fast yet?
References: <alpine.LNX.2.02.1206280529320.4288@localhost.localdomain> <20120701163843.389a4e2b@sf.home>

On Sun, 1 Jul 2012, Sergei Trofimovich wrote:

* Unfortunately Callgrind doesn't save the full stack trace so what you
see is a statistical breakdown for callees. It doesn't necessarily mean
that a call path displayed actually exists deeper than its first level.
But the numbers add-up so this is minor.

You might give a try to --num-callers= valgrind's option.

Thanks for the tip, but it doesn't seem to help. The reason is that Callgrind's output format only tells you that you call a function X number of times from function Y. So you may only assume that you've reached function Y from any of its callers.

Dimitris

References:
- Re: Are we fast yet?
  - From: Sergei Trofimovich

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]