public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: JAY LULLA <JAY.LULLA@Sun.COM>
To: help-gcc@gnu.org
Subject: tools for getting call-graph info after compilation
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <387540DC.C07890F7@Sun.COM> (raw)
Message-ID: <20000401000000.cHaBEZREus4Y_y1SLH1hdvrsqqa4V1WFMmIfbtj_mQE@z> (raw)

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

             reply	other threads:[~2000-04-01  0:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-06 17:39 JAY LULLA [this message]
2000-01-07 10:26 ` Phil McRevis
2000-04-01  0:00   ` Phil McRevis
2000-04-01  0:00 ` JAY LULLA

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=387540DC.C07890F7@Sun.COM \
    --to=jay.lulla@sun.com \
    --cc=help-gcc@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).