From: Guillaume Hennequin <gje.hennequin@gmail.com>
To: caml-list@yquem.inria.fr
Subject: OCaml and GPUs
Date: Wed, 9 Sep 2009 12:42:35 +0200 [thread overview]
Message-ID: <d8e32b760909090342x532f98bfm8232d86ea6f74177@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 626 bytes --]
Hello,
I was wondering if there has been any effort so far in interfacing OCaml
with GPU programming solutions like AMD Stream, or OpenCL.
I'm only aware of Daml (CUDA bindings).
I wrote some pieces of AMD Brook bindings a while ago to do very basic
read/write operations on GPU, plus some kernel calls.
I don't have much time to invest in this unfortunately.
With OpenCL's ability to compile kernels at runtime, bindings for Ocaml
could even offer the nice possibility to write the kernels in .ml files as
strings, which would save a lot of wrappers around kernel-only C files.
any ideas, comments, pointers ?
Guillaume.
[-- Attachment #2: Type: text/html, Size: 682 bytes --]
next reply other threads:[~2009-09-09 10:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 10:42 Guillaume Hennequin [this message]
2009-09-09 12:37 ` [Caml-list] " Sashan Govender
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=d8e32b760909090342x532f98bfm8232d86ea6f74177@mail.gmail.com \
--to=gje.hennequin@gmail.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;
as well as URLs for NNTP newsgroup(s).