From: "David Allsopp" <dra-news@metastack.com>
To: "'Basile STARYNKEVITCH'" <basile@starynkevitch.net>,
"'Eray Ozkural'" <examachine@gmail.com>
Cc: <caml-list@inria.fr>
Subject: RE: [Caml-list] How to write a CUDA kernel in ocaml?
Date: Wed, 16 Dec 2009 00:18:57 +0100 [thread overview]
Message-ID: <017101ca7ddc$fb936b20$f2ba4160$@allsopp@metastack.com> (raw)
In-Reply-To: <4B27B981.80700@starynkevitch.net>
Basile Starynkevitch wrote:
> Eray Ozkural wrote:
>
> Compiling Ocaml to efficient C is not easy and probably impossible (or
> extremely difficult) in the general case. In
> particular, tail recursive calls are essential in Ocaml, and are not
> available in C in most compilers.
What's this based on (out of interest)? Most C compilers don't necessarily
identify tail recursion in *C* code but if you're emitting C as an OCaml
backend then there's no reason not to convert tail recursive *OCaml*
functions to C code based on goto or similar looping constructs (yes, you'd
almost-always-virtually-never use goto in a hand-crafted C program without
apologising profusely at Dijkstra's grave but if you're using C as an
intermediate language then that's a different matter). If I recall correctly
from an old post on this list, this is how Felix handles tail recursion when
translating Felix to C++
David
next prev parent reply other threads:[~2009-12-15 23:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 15:37 Eray Ozkural
2009-12-15 16:07 ` [Caml-list] " Basile STARYNKEVITCH
2009-12-15 16:20 ` Eray Ozkural
2009-12-15 16:29 ` Basile STARYNKEVITCH
2009-12-15 17:46 ` Eray Ozkural
2009-12-15 23:18 ` David Allsopp [this message]
2009-12-16 0:39 ` Jon Harrop
2009-12-16 13:41 ` Mattias Engdegård
2009-12-16 13:47 ` Eray Ozkural
2009-12-17 0:34 ` Philippe Wang
2009-12-17 6:45 ` Eray Ozkural
2009-12-17 10:59 ` Philippe Wang
2010-01-12 6:15 ` Eray Ozkural
2009-12-16 6:26 ` Basile STARYNKEVITCH
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='017101ca7ddc$fb936b20$f2ba4160$@allsopp@metastack.com' \
--to=dra-news@metastack.com \
--cc=basile@starynkevitch.net \
--cc=caml-list@inria.fr \
--cc=examachine@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