From: Oleg <oleg@okmij.org>
To: "aroseunsaid@proton.me" <aroseunsaid@proton.me>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] 3 questions relating to BER MetaOcaml
Date: Tue, 30 May 2023 13:45:47 +0100 [thread overview]
Message-ID: <ZHXv+0UAFC/BOFeo@Magus.localnet> (raw)
In-Reply-To: <kZmnx68M29GrM6ZHc-PQULtY03qJZAW1REo0NwQIPOODKZUGZd0Og-Yw4yI3hmjr_rrAcAU24zRdh8-JZKRHbGg3eHt0UwGrx-oQTslSLa4=@proton.me>
Hello!
> 1. Is there a mailing-list or any other forum dedicated to MetaOcaml,
> or also metaprogramming in other languages than OCaml?
I personally don't know of any. Which is somewhat strange come to
think of it. In the past, the questions about MetaOCaml were either
posted on this list (like yours) or sent to me privately.
> 2. Is anybody using BER MetaOcaml having done some work to offshore to
> intel's ISPC or OpenGL GLSL both having the semantic (and keywords) of
> "uniform" vs "varying" variables for optimizing code accross code
> threads (cores / SIMD "lane")? If so, are they willing to share their
> work?
That does look quite interesting. A student once used offshoring for
OpenCL (which is quite C but not exactly). Incidentally, one of the
tests of MetaOCaml, at the end of
OCAMLROOT/metalib/test/offshore_simple.ml
is a very simplified version of some of that code.
> 3. There is no trx.cmo in the current opam 4.14.1+BER switch, is it
> intentional, a current BER limitation or an overlook?
Overlook -- or, better, ignorance. I put trx.cmx into the libpath
because otherwise the native compiler complains. I didn't think
trx.cmo is needed for anything. It is part of ocamlcommon.cma though.
prev parent reply other threads:[~2023-05-30 12:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 18:28 A Rose Unsaid
2023-05-30 12:45 ` Oleg [this message]
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=ZHXv+0UAFC/BOFeo@Magus.localnet \
--to=oleg@okmij.org \
--cc=aroseunsaid@proton.me \
--cc=caml-list@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