Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Laszlo Nemeth <laszlo@ropas.kaist.ac.kr>
To: caml-list@inria.fr
Subject: [Caml-list] List of code optimisations performed by ocamlc
Date: Fri, 8 Jun 2001 11:06:49 +0900 (KST)	[thread overview]
Message-ID: <200106080206.LAA10209@ropas.kaist.ac.kr> (raw)

Hi,


Is there a list (or discussion) of code optimisations performed by the
caml family of compilers? I'd be interested in both the different
optimisations and their ordering. I had a quick look at the source,
but a higher level view would be much simpler.

I'd appreciate pointers, papers, etc.

Thanks,
  Laszlo

PS. I know the papers in caml.inria.fr/ocaml/papers (in particular the
ZINC paper). I also had a look at the archives, but only found a few
comments regarding particular optimisations.
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr


                 reply	other threads:[~2001-06-08  2:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200106080206.LAA10209@ropas.kaist.ac.kr \
    --to=laszlo@ropas.kaist.ac.kr \
    --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