From: Xavier Leroy <xavier.leroy@inria.fr>
To: "Yaron M. Minsky" <yminsky@CS.Cornell.EDU>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] generating a call-graph
Date: Mon, 26 May 2003 11:14:16 +0200 [thread overview]
Message-ID: <20030526111416.A31160@pauillac.inria.fr> (raw)
In-Reply-To: <52762.141.155.88.179.1053707680.squirrel@minsky-primus.homeip.net>; from yminsky@CS.Cornell.EDU on Fri, May 23, 2003 at 12:34:40PM -0400
> Does anyone know a way of generating a call-graph from a set of ocaml
> sources? What I want to do is, at a minimum, get a list of all the
> functions that could be called as a result of a given function invocation.
This requires a non-trivial static analysis called "control flow
analysis" in the literature; particular instances include Shivers'
0-CFA and k-CFA, Jagannathan and Wright's "polymorphic splitting",
etc.
The difficulty is that functions are first-class values, so the
function you're applying can be a parameter to another function, or a
member of a data structure. (Objects raise similar issues.)
Thus, the control flow cannot be determined independently of the data
flow, and "control flow analysis" is really a data flow analysis that
tracks the flow of functional values.
I don't know of any implementation of control-flow analysis for the
whole OCaml language.
- Xavier Leroy
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-05-26 9:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 16:34 Yaron M. Minsky
2003-05-26 0:51 ` Jeff Henrikson
2003-05-26 9:14 ` Xavier Leroy [this message]
2003-06-03 4:27 ` John Max Skaller
2003-05-27 2:40 ` Jeff Henrikson
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=20030526111416.A31160@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=yminsky@CS.Cornell.EDU \
/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 NNTP newsgroup(s).