From: Jan Kybic <kybic@fel.cvut.cz>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] AST versus Ocaml
Date: Wed, 04 Nov 2009 23:21:24 +0100 [thread overview]
Message-ID: <87y6mmc4nv.fsf@fel.cvut.cz> (raw)
In-Reply-To: <200911042025.34897.jon@ffconsultancy.com> (Jon Harrop's message of "Wed, 4 Nov 2009 20:25:34 +0000")
> I haven't found the time to give ATSLang a serious test drive but I had a
> brief conversation with Hongwei Xi about his work and goals. He is into
> systems programming, which is closely related to high performance programming
> in the context of serial code but foundations for easy parallel programming
> are missing.
Jon, thank you for your comments. Parallel programming support through
threads is not a showstopper for me - my problems can usually be
parallelized easily using processes or via message passing (on a cluster).
> like non-blocking algorithms might be tricky. Another concern is that ATS'
> code gen goes via GCC and GCC is quite a sucky compiler with poor compilation
I am not worried about that either, I have been living happily with
gcc for a long time and if needed, I imagine that the code can be
compiled by another C compiler.
> and crashes rather than performance. Moreover, I would note that the
> performant ATS code out there seems to go to *great* lengths to avoid the GC
> whenever possible, so I suspect it is extremely slow in the context of
> heavily allocating code or many short-lived values (much like HLVM). For
This will be easy to test.
> My vision for the OCaml+HLVM combo is the ability to use HLVM from your OCaml
> projects to generate and execute high performance parallel numerical code
> on-the-fly.
So you do not plan to write a full compiler for Ocaml with HLVM
output? That would be disappointing. I must say, I do not have much need to
generate and execute code on the fly. I was hoping that Ocaml+HLVM
would allow me to write a more generic code without the performance
penalty it now incurs.
> In the meantime, you can still use HLVM to generate serial numerical code that
> is typically 2-3x faster than the equivalent OCaml code.
Yes, but if I understand correctly, the language you can use for that
is rather restricted. If I write a code like that (no polymorphic
functions, no functors, no objects), Ocaml is already fast enough for
me. And are you not better off using for example MetaOcaml with
offshoring to C?
Yours,
Jan
--
-------------------------------------------------------------------------
Jan Kybic <kybic@fel.cvut.cz> tel. +420 2 2435 5721
http://cmp.felk.cvut.cz/~kybic ICQ 200569450
next prev parent reply other threads:[~2009-11-04 22:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 14:01 Jan Kybic
2009-11-04 14:41 ` [Caml-list] " Kevin Cheung
2009-11-04 15:42 ` Jan Kybic
2009-11-04 20:25 ` Jon Harrop
2009-11-04 22:21 ` Jan Kybic [this message]
2009-11-04 23:15 ` Jon Harrop
2009-11-06 11:48 ` [Caml-list] ATS " Jan Kybic
2009-11-06 12:11 ` Sylvain Le Gall
2009-11-06 15:38 ` [Caml-list] " Jan Kybic
2009-11-07 1:56 ` Jacques Garrigue
2009-11-07 19:00 ` Jon Harrop
2009-11-06 12:22 ` [Caml-list] " Mauricio Fernandez
2009-11-04 15:37 ` [Caml-list] AST " malc
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=87y6mmc4nv.fsf@fel.cvut.cz \
--to=kybic@fel.cvut.cz \
--cc=caml-list@yquem.inria.fr \
--cc=jon@ffconsultancy.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