From: Benedikt Meurer <benedikt.meurer@googlemail.com>
To: caml-list@yquem.inria.fr
Subject: Re: ocamlopt LLVM support (Was: [Caml-list] OCamlJIT2 vs. OCamlJIT)
Date: Sun, 5 Dec 2010 21:54:26 +0100 [thread overview]
Message-ID: <531273EC-18C6-46EA-8AAB-1D5F1A412A0C@googlemail.com> (raw)
In-Reply-To: <20101205185711.0a0e485a@deb0>
On Dec 5, 2010, at 17:57 , Török Edwin wrote:
> On Sun, 5 Dec 2010 17:37:32 +0100
> Benedikt Meurer <benedikt.meurer@googlemail.com> wrote:
>
>> Two main areas for now: The GC interface and the exception handling.
>> LLVM's exception support is really limited; the GC support is better
>> and more generic. I don't know how to implement the OCaml exception
>> model within LLVM w/o adding a lot of special case stuff to LLVM
>> itself (mentioned in my original post); if there would be a way to
>> easily extend LLVM with special exception models, other projects
>> could plug in their models.
>
> There is a discussion on the LLVM mailing list about changing exception
> handling in LLVM:
> http://lists.cs.uiuc.edu/pipermail/llvmdev/2010-December/036692.html
>
> If the new model is not generic enough to support OCaml's model, then I
> think now would be a good time to describe on the LLVM ML what OCaml's
> model would need and the proposal doesn't cover.
It's not a different model, but a better implementation of what is already available. From what I've seen now, the best starting point seems to be the setjmp/longjmp model, which is supported by LLVM. It's certainly slower than the current scheme, but well, it would be a starting point.
> Best regards,
> --Edwin
Benedikt
next prev parent reply other threads:[~2010-12-05 20:54 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
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 [this message]
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=531273EC-18C6-46EA-8AAB-1D5F1A412A0C@googlemail.com \
--to=benedikt.meurer@googlemail.com \
--cc=caml-list@yquem.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