From: "Török Edwin" <edwintorok@gmail.com>
To: Eray Ozkural <examachine@gmail.com>
Cc: Till Varoquaux <till@pps.jussieu.fr>, caml-list@yquem.inria.fr
Subject: Re: ocamlopt LLVM support (Was: [Caml-list] OCamlJIT2 vs. OCamlJIT)
Date: Fri, 3 Dec 2010 16:06:56 +0200 [thread overview]
Message-ID: <20101203160656.4d48ce68@deb0> (raw)
In-Reply-To: <AANLkTinMeVSdQmM-zyjFiLyROq87iyO8E9nbT6Ac4EaE@mail.gmail.com>
On Fri, 3 Dec 2010 15:41:41 +0200
Eray Ozkural <examachine@gmail.com> wrote:
> Is there IPA in LLVM? I didn't know that.
>
See createStandardLTOPasses and the UnitAtATime part of
createStandardModulePasses:
http://llvm.org/svn/llvm-project/llvm/trunk/include/llvm/Support/StandardPasses.h
Also
http://llvm.org/svn/llvm-project/llvm/trunk/include/llvm/Transforms/IPO.h
http://llvm.org/svn/llvm-project/llvm/trunk/lib/Analysis/IPA
I doubt they'll be able to figure out everything on their own though,
the frontend should probably add some extra info. For example
by adding some function attributes, or some metadata about the
high-level types.
I see that LLVM has a metadata based TBAA, but right now it is for
C/C++, so I'm not sure it could take advantage of all the properties of
a functional language.
It'd probably be better if an OCamlAA was written (perhaps building on
the already existing TBAA, or improving that) that takes advantage of
immutable data structures and OCaml's type system.
Best regards,
--Edwin
next prev parent reply other threads:[~2010-12-03 14:07 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 8:36 OCamlJIT2 vs. OCamlJIT Benedikt Meurer
2010-11-30 10:48 ` [Caml-list] " Török Edwin
2010-11-30 10:55 ` Benedikt Meurer
2010-11-30 17:01 ` bluestorm
2010-11-30 17:26 ` Török Edwin
2010-11-30 18:27 ` Basile Starynkevitch
2010-11-30 17:29 ` Benedikt Meurer
2010-11-30 17:32 ` Yoann Padioleau
2010-11-30 22:06 ` Jon Harrop
2010-11-30 22:48 ` Benedikt Meurer
2010-12-01 14:11 ` Jon Harrop
2010-12-01 15:00 ` Benedikt Meurer
2010-12-01 22:03 ` Jon Harrop
2010-12-02 1:17 ` Eray Ozkural
2010-12-03 10:03 ` ocamlopt LLVM support (Was: [Caml-list] OCamlJIT2 vs. OCamlJIT) Benedikt Meurer
2010-12-03 13:34 ` Till Varoquaux
2010-12-03 13:41 ` Eray Ozkural
2010-12-03 14:06 ` Török Edwin [this message]
2010-12-03 21:16 ` Jon Harrop
2010-12-05 16:44 ` Benedikt Meurer
2010-12-03 14:32 ` Philippe Strauss
2010-12-03 21:22 ` Jon Harrop
2010-12-03 21:45 ` Philippe Strauss
2010-12-03 15:32 ` Michael Ekstrand
2010-12-03 21:34 ` Jon Harrop
2010-12-03 20:07 ` Jon Harrop
2010-12-05 16:37 ` Benedikt Meurer
2010-12-05 16:57 ` Török Edwin
2010-12-05 20:54 ` Benedikt Meurer
2010-12-05 20:12 ` Jon Harrop
2010-12-05 21:21 ` Benedikt Meurer
2010-12-05 21:44 ` Benedikt Meurer
2010-12-06 22:38 ` Jon Harrop
2010-12-05 22:41 ` Erik de Castro Lopo
2010-12-05 22:34 ` Erik de Castro Lopo
2010-12-06 8:27 ` Benedikt Meurer
2010-12-06 9:28 ` David Rajchenbach-Teller
2010-12-06 11:08 ` Richard Jones
2010-12-06 20:18 ` Jon Harrop
2010-12-01 0:16 ` [Caml-list] OCamlJIT2 vs. OCamlJIT Erik de Castro Lopo
2010-12-01 1:34 ` Yoann Padioleau
2010-12-01 12:58 ` Jon Harrop
2010-12-01 13:55 ` ivan chollet
2010-11-30 21:19 ` Jon Harrop
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=20101203160656.4d48ce68@deb0 \
--to=edwintorok@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=examachine@gmail.com \
--cc=till@pps.jussieu.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).