This is the mail archive of the gcc-help@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]

tools for getting call-graph info after compilation


Hi. I was wondering if anyone knows of GNU tools that can generate
call-graph info while compiling and linking a big multi-file program.

This info shows
which functions call other functions. If it is possible to get a nice
graph / tree / table of this info, that would be great. If that is not
possible, we would be glad to get the raw data in text form.

For example, one minimal way to represent the data would be a matrix:

                Func A  Func B  Func C  ...     Func X
function A      0       1       1               0
func    B       0       0       1               1
func    C       1       0       0               0
.
.
func    X       0       1       0               0

ie 1's or 0's represent whether the function in the column is called by
the function in the row.

Since this info is independent of run-time behavior, it should be
possible to get the info after compilation.
--------------------------------------------
I believe that there is a tool called "gcov" which indicates which parts
of the code are covered by input data, but I believe that it is a
run-time tool, not one that shows the structural info from compilation.

Nonetheless, if you have used "gcov", perhaps you can send me some info
on its use, and at what step in compiling / linking (/ running) the
program you use it.
---------------------------------------------

Thanks!

Jay Lulla
jay.lulla@ebay.sun.com

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