Re: callgraph collection

[Ray B. <ra...@sg...>]

Call graph profiling is needed to distinguish between the static call gra=
ph,
which is what you get from compile time analysis, and the dynamic call gr=
aph,
which is what the program actually does.  It answers the question "What w=
as
actually called and how often" versus the compile time analysis "which te=
lls
you what COULD be called".  The actual usage information obtained from th=
e
call graph is what is useful for performance optimization.

J=F6rn Engel wrote:
> On Mon, 12 January 2004 16:37:10 -0500, Will Cohen wrote:
>=20
>>I have started to look over the OProfile patch for the call graphs at=20
>>http://perso.wanadoo.fr/phil.el/.
>=20
>=20
> What do you need the call graphs for?
>=20
> The reason I ask is that I can statically generate call graphs when
> compiling the kernel, including indirect calls through function
> pointers.  Both graphs will be quite different, since mine is the
> theoretically possible one, while yours is practically experienced, so
> it will contain fewer calls.  So you may still need to go through
> oprofile, depending on what you do with the data.
>=20
> J=F6rn
>=20

--=20
Best Regards,
Ray
-----------------------------------------------
                   Ray Bryant
512-453-9679 (work)         512-507-7807 (cell)
ra...@sg...             ra...@au...
The box said: "Requires Windows 98 or better",
            so I installed Linux.
-----------------------------------------------