From: Philippe Wang <philippe.wang@lip6.fr>
To: caml-list@inria.fr
Cc: Philippe Wang <philippe.wang@lip6.fr>
Subject: ocamlclean : an OCaml bytecode cleaner (Was: (Announce) "OCAPIC" : OCaml for PIC18 microcontrollers)
Date: Thu, 11 Nov 2010 02:09:03 +0100 [thread overview]
Message-ID: <26FB93F3-065E-46C0-9767-0244B419626D@lip6.fr> (raw)
In-Reply-To: <2728CE5E-1335-4D6B-983D-305E6E5DA344@lip6.fr>
Dear all,
Shortly:
ocamlclean is now available in a separate package so that you don't have to get the whole ocapic distribution just to try ocamlclean.
More information:
ocamlclean takes a bytecode executable (which are generally but not necessarily produced by "ocamlc" compiler) and reduces its size by eliminating some dead code. Dead code is discriminated statically. (It's impossible to eliminate all dead code, but in some cases it can reduce bytecode executables tremendously) It is meant to be compatible with standard bytecode such as produced by ocamlc. (DBUG section is currently not supported and is removed during the cleaning process. Other unsupported sections are left untouched.)
Web site:
http://www.algo-prog.info/ocaml_for_pic/
Developer:
Benoît Vaugon
--
Philippe Wang
http://www-apr.lip6.fr/~pwang/
next prev parent reply other threads:[~2010-11-11 1:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <951AD91B-DA92-4F92-AE90-86A13DDB2357@lip6.fr>
2010-11-04 21:44 ` (Announce) "OCAPIC" : OCaml for PIC18 microcontrollers Philippe Wang
2010-11-05 12:35 ` [Caml-list] " Daniel Bünzli
2010-11-05 14:26 ` Philippe Wang
2010-11-06 17:47 ` Goswin von Brederlow
2010-11-06 19:19 ` Philippe Wang
2010-11-11 1:09 ` Philippe Wang [this message]
2010-11-11 5:52 ` [Caml-list] ocamlclean : an OCaml bytecode cleaner (Was: (Announce) "OCAPIC" : OCaml for PIC18 microcontrollers) Julien Signoles
2010-11-11 11:57 ` Philippe Wang
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=26FB93F3-065E-46C0-9767-0244B419626D@lip6.fr \
--to=philippe.wang@lip6.fr \
--cc=caml-list@inria.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).