Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Benedikt Rosenau <Benedikt.Rosenau@dlr.de>
To: caml-list@inria.fr
Subject: Platforms and OCaml
Date: Wed, 2 Aug 2000 16:49:32 +0200 (DFT)	[thread overview]
Message-ID: <200008021449.e72EnW991530@dv.go.dlr.de> (raw)


Hello,

I am new to this list and fairly new to OCaml as well. To
my other shortcomings belongs that I do not speak French
except for a few phrases. 

Nonetheless, I have some questions regarding the possible
use of OCaml on vector computers. Vector computers work by
putting iterated pieces of code on an "assembly line", so
that each part of the assembly line does one specified
operation on its operands and feeds its output into the next
station on the assembly line.

The trouble with vector computers is that this induces a
fixed order of evaluation for the iterated code. Or the
other way around: given a certain loop, the compiler has to
find out whether this loop is vectorizable, and that task
is non-trivial. Further, there are only so many operations,
mostly numeric operations, provided by the vector units.

Now, I think that a vectorizing compiler for OCaml is a
nice vision, almost as nice as world peace, yet I wonder
if OCaml cannot be put to a different use. I may be off
track here, but it seems that abstract datatypes together
with an interface to an existing and vectorizing C compiler
might do the trick.

One way to convince the compiler that a certain piece of
code may be vectorized would be to provide the "assembly
line" as a datatype and to ensure that only functions based
on the operations in the vector unit get applied to data
of this type. From my naive point of view, Bigarrays seem
promising, but maybe streams would fare better.

Comments, critique? Do I make sense at all?
   Benedikt



                 reply	other threads:[~2000-08-03 13:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200008021449.e72EnW991530@dv.go.dlr.de \
    --to=benedikt.rosenau@dlr.de \
    --cc=Benedikt.Rosenau@debis-sfr.de \
    --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