From: Benedikt Meurer <benedikt.meurer@googlemail.com>
To: Wojciech Meyer <wojciech.meyer@googlemail.com>
Cc: caml-list@inria.fr, Marcell Fischbach <marcellfischbach@googlemail.com>
Subject: Re: [Caml-list] Linear Scan Register Allocator for ocamlopt/ocamlnat
Date: Mon, 1 Aug 2011 19:03:13 +0200 [thread overview]
Message-ID: <182A8FD1-44FC-4772-8094-E74B0BD68166@googlemail.com> (raw)
In-Reply-To: <CAOg1smBk+vn61unew+MeY=rk_mQGWN-L0iwFst=C-DUnL2n+vQ@mail.gmail.com>
On Aug 1, 2011, at 17:29 , Wojciech Meyer wrote:
> Hello Benedikt,
Hello Wojciech,
> It's also worth to note that there is some generic mid/back-end code ready, in my OCaml native compiler framework called DragonKit in a spirit of LLVM, which I am currently actively working on. It's already able to express a toy language and JIT compile and run it within the same process on top of x86 architecture:
>
> The code includes:
> - SSA based IL using polymorphic variants
> - monadic code generator
> - plugable passes using first class modules
> - very ad-hoc register allocator
> - X86 backend
> - example that evolved from LLVM kaleidoscope ported to DragonKit to Pascal/ML like language, and another example using direct translation to X86 backend.
>
> The code is functorised and almost purely functional (with few exceptions where there is no benefit of doing that).
>
> Maybe it could have some use in your new toplevel, or maybe it would be worth to reuse some of your work in DragonKit (or viceversa).
>
> I welcome anybody wanting to join me in this effort.
>
> Please take a look at:
>
> www.github.com/danmey/DragonKit
I doubt that this would be applicable in the context of ocamlopt. What we are heading for is simply a way to avoid the external as and ld invocations by doing the work in-process. Code generation is done already, we just replace the last phase (see emit.ml).
BTW: On a related note, we also have a student working on a LLVM backend for ocamlopt as part of his bachelor thesis, which may be related to what you do.
> Cheers;
> Wojciech
greets,
Benedikt
prev parent reply other threads:[~2011-08-01 17:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 14:53 Benedikt Meurer
2011-08-01 15:03 ` [Caml-list] " Benedikt Meurer
2011-08-01 15:04 ` [Caml-list] " Gabriel Scherer
2011-08-01 16:57 ` Benedikt Meurer
2011-08-24 19:35 ` Benedikt Meurer
2011-08-24 20:40 ` Gerd Stolpmann
2011-08-25 8:02 ` Benedikt Meurer
2011-08-25 9:34 ` Benedikt Meurer
2011-08-25 10:21 ` Gerd Stolpmann
2011-08-25 10:25 ` Pierre-Alexandre Voye
2011-08-26 10:58 ` Guillaume Yziquel
2011-08-26 12:29 ` Erik de Castro Lopo
[not found] ` <CANnJ5GfmnOhk8mJor8PfrGoC1-5vZWOgUKNZMT9k69iu0TBCeA@mail.gmail.com>
[not found] ` <CANnJ5Gf4AnKPDvrKiYx0joiPbQVOCdFWgPR24Y1ZYYL1Qv5=fg@mail.gmail.com>
2011-08-26 18:33 ` Pierre-Alexandre Voye
2011-08-30 21:07 ` Fermin Reig
2011-08-30 21:21 ` Pierre-Alexandre Voye
2011-08-25 10:43 ` Benedikt Meurer
2011-08-24 20:47 ` malc
2011-08-26 12:40 ` Roberto Di Cosmo
2011-08-01 15:29 ` Wojciech Meyer
2011-08-01 17:03 ` Benedikt Meurer [this message]
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=182A8FD1-44FC-4772-8094-E74B0BD68166@googlemail.com \
--to=benedikt.meurer@googlemail.com \
--cc=caml-list@inria.fr \
--cc=marcellfischbach@googlemail.com \
--cc=wojciech.meyer@googlemail.com \
/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