caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Eric Dahlman <edahlman@atcorp.com>
To: caml-list <caml-list@inria.fr>
Cc: Nicolas Cannasse <warplayer@free.fr>,
	"<skaller@users.sourceforge.net>" <skaller@users.sourceforge.net>,
	David MENTRE <dmentre@linux-france.org>
Subject: Re: [Caml-list] unused function detection
Date: Tue, 22 Jun 2004 13:38:14 -0500	[thread overview]
Message-ID: <525AEC07-C47B-11D8-A9FD-000393914EAA@atcorp.com> (raw)
In-Reply-To: <008201c45882$b3532560$19b0e152@warp>


Some old lisp systems had this ability they would identify that bit of 
your program needed to support a given set of functions and allow you 
to purge the rest.  There were some constraints on what the program 
could do (no applying random symbols for example) and possibly some 
heuristics as well.  The name for this process was "tree shaking" if 
anyone is interested in looking into what was involved.  A quick google 
search on my part surprised me with the size of both the christmas tree 
and pecan industries on the net, but little of real interest.

-Eric

On Jun 22, 2004, at 12:59 PM, Nicolas Cannasse wrote:

>> skaller <skaller@users.sourceforge.net> writes:
>>
>>> Can Ocaml find unused functions, or does someone happen
>>> to have a tool lying around that does so?
>>
>> Use ocaml profiling tools to find function called zero times?
>>
>> Yours,
>> d.
>
> That's not complete enough, since the behavior - then the code 
> executed - of
> the application might depend of different kind of inputs : network, 
> user,
> command line, ...
> Since there is no guarantee that after removing the functions called 
> zero
> time, you program will even compile , what he needs is actually a 
> statical
> analysis tool using a code coverage algorithm, given one or more entry
> points. This analysis can find without even executing the program the 
> most
> small subset of functions needed in order to compile the applications.
> That's actually quite an interesting piece of code to write in a 
> functional
> language, and it would be nice if it can detects also unused *types*.
>
> Regards,
> Nicolas Cannasse
>
> -------------------
> 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
>

-------------------
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


  parent reply	other threads:[~2004-06-22 18:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-22 17:08 skaller
2004-06-22 17:31 ` David MENTRE
2004-06-22 17:59   ` Nicolas Cannasse
2004-06-22 18:32     ` skaller
2004-06-22 18:33     ` Michael Furr
2004-06-22 19:27       ` skaller
2004-06-22 19:46         ` Michael Furr
2004-06-22 18:38     ` Eric Dahlman [this message]
2004-06-22 19:18       ` skaller
     [not found] <fa.edndqci.a2eggi@ifi.uio.no>
2011-02-08 10:52 ` Radu Grigore
2011-02-08 12:30   ` Gabriel Scherer
2011-02-09  0:02     ` Jerome Benoit

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=525AEC07-C47B-11D8-A9FD-000393914EAA@atcorp.com \
    --to=edahlman@atcorp.com \
    --cc=caml-list@inria.fr \
    --cc=dmentre@linux-france.org \
    --cc=skaller@users.sourceforge.net \
    --cc=warplayer@free.fr \
    /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).