From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Ocamlopt code generator question
Date: Tue, 5 May 2009 16:14:52 +0100 [thread overview]
Message-ID: <200905051614.52276.jon@ffconsultancy.com> (raw)
In-Reply-To: <4A004A05.6040204@lexifi.com>
On Tuesday 05 May 2009 15:15:33 Jean-Marc Eber wrote:
> Hi Dimitry,
>
> LexiFi for instance _is_ clearly interested by a sse2 32bit code generator.
>
> One should probably have the following in mind and/or ask the following
> questions:
>
> - it is probably not a good idea to support both backends (sse2 and old
> stack fp i386 architecture). It will be necessary to make a choice
> (especially taking in account the limited INRIA resources and the burden of
> already supporting different windows ports).
>
> - would INRIA be ok to switch to a sse2 code generator (based on Dimitry's
> patch - supposing that he is ok to donate it to INRIA - or Xavier's work or
> whatever)?
>
> - I also guess that a sse2 code generator would be simpler than the current
> one (that has to support this horrible fp stack architecture) and would
> therefore be a better candidate for further enhancements.
>
> - what is the opinion on this list, as a switch to a sse2 backend would
> exclude "old" processors from being OCaml compatible (I don't have a
> precise list at hand for now) ?
>
> My opinion is that this support of legacy hardware is not important, but I
> guess others are arguing in opposite directions... :-)
>
> But again, having better floating point performance (and predictable
> behaviour, compared to the bytecode version) would be a big plus for some
> applications.
If the idea is to provide better code generation on x86 going forwards with
minimal effort then I'd have thought an LLVM-based backend would be the
obvious choice. My tests with HLVM showed that numerical code can be a
whopping 8x faster than today's ocamlopt on x86 and, of course, LLVM is
improving much more rapidly.
LLVM can probably replace the x86, x64 and ppc backends. LLVM also seems like
a sane approach to providing a native-code top level via its existing JIT
functionality.
--
Dr Jon Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/?e
next prev parent reply other threads:[~2009-05-05 15:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 19:36 Dmitry Bely
[not found] ` <m27i13tofi.fsf@Pythagorion.local.i-did-not-set--mail-host-address--so-tickle-me>
2009-04-29 16:50 ` Dmitry Bely
2009-04-29 20:04 ` Jeffrey Scofield
2009-05-05 9:24 ` [Caml-list] " Xavier Leroy
2009-05-05 9:41 ` Dmitry Bely
2009-05-05 14:15 ` Jean-Marc Eber
2009-05-05 14:58 ` Sylvain Le Gall
2009-05-05 15:21 ` [Caml-list] " David Allsopp
2009-05-05 15:59 ` Dmitry Bely
[not found] ` <4A006410.8000205@lexifi.com>
2009-05-05 16:26 ` Dmitry Bely
2009-05-05 15:14 ` Jon Harrop [this message]
2009-05-08 10:21 ` [Caml-list] Ocamlopt x86-32 and SSE2 Xavier Leroy
2009-05-10 11:04 ` David MENTRE
2009-05-11 2:43 ` Jon Harrop
2009-05-11 3:43 ` Stefan Monnier
2009-05-11 5:38 ` [Caml-list] " Jon Harrop
2009-05-10 23:12 ` [Caml-list] " Matteo Frigo
2009-05-11 2:45 ` Jon Harrop
2009-05-11 7:55 ` Dmitry Bely
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=200905051614.52276.jon@ffconsultancy.com \
--to=jon@ffconsultancy.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