From: Guillaume Yziquel <guillaume.yziquel@citycable.ch>
To: Pierre-Alexandre Voye <ontologiae@gmail.com>
Cc: Gerd Stolpmann <info@gerd-stolpmann.de>,
Benedikt Meurer <benedikt.meurer@googlemail.com>,
caml-list@inria.fr,
Fischbach Marcell <marcellfischbach@googlemail.com>
Subject: Re: [Caml-list] Linear Scan Register Allocator for ocamlopt/ocamlnat
Date: Fri, 26 Aug 2011 12:58:18 +0200 [thread overview]
Message-ID: <20110826105818.GZ4564@localhost> (raw)
In-Reply-To: <CANnJ5Gc9xsx6EdZTNW5EkO5giZ59s5JogzM4Y48=WJLF1SwpZg@mail.gmail.com>
Le Thursday 25 Aug 2011 à 12:25:49 (+0200), Pierre-Alexandre Voye a écrit :
> I have a stupid question : I wonder if it would not be a bad idea that
> Ocaml output C code and let gcc do its work, so compile code with good
> performances in a lot of architecture ? Gcc is able to do
> autovectorization (SSE, MMX, Larabee in the futur, etc...), very
> specific processor optimization, etc...
> But maybe it's a stupid idea ?
I do not think it's a stupid idea. I've been quite stunned by how the
Mercury compiler does it (using cpp macros and so-called virtual
registers in C code). It's likely a pain however, and most compilers
I've seen using the "compile to C" approach usually use Boehm's GC, so
it may be quite a pain to adapt the OCaml runtime to it. However, gcc
isn't the golden bullet for everything. It definitely sucks with the
SIMD instruction set.
--
Guillaume Yziquel
next prev parent reply other threads:[~2011-08-26 10:59 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 [this message]
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
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=20110826105818.GZ4564@localhost \
--to=guillaume.yziquel@citycable.ch \
--cc=benedikt.meurer@googlemail.com \
--cc=caml-list@inria.fr \
--cc=info@gerd-stolpmann.de \
--cc=marcellfischbach@googlemail.com \
--cc=ontologiae@gmail.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;
as well as URLs for NNTP newsgroup(s).