caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jonathan Roewen <jonathan.roewen@gmail.com>
To: Oliver Bandel <oliver@first.in-berlin.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] doing MMX through ocaml
Date: Fri, 18 Nov 2005 10:57:29 +1300	[thread overview]
Message-ID: <ad8cfe7e0511171357j23b36f73n43c2ae9c682419ec@mail.gmail.com> (raw)
In-Reply-To: <20051117214745.GA580@first.in-berlin.de>

> ASM...MMX.... will the OS be available for more than one platform?

Right now, no. Later, possibly. If can abstract MMX enough, could use
cpuid to choose altivec for example on PPC. And this would be done at
init time (much like filename.ml handles platform choice automatically
at init time).

Another question =)

I've used -dinstr to observe the bytecode instructions that are
generated (though obviously not yet optimised as it pushes a value,
then pops it back into accumulator straight away).

Now, how can I find out what the actual generated instructions are
that correspond to those in interp.c? I'm trying to get an idea of the
performance of calling single MMX asm instructions from ocaml, rather
than create special functions that do a bunch at a time.

Like, does CHECK_SIGNALS get interweaved between two ccalls? Like in
the following -dinstr dump:

  const 5
  push
  acc 0
  ccall neg, 1
  ccall incr, 1

Jonathan


  reply	other threads:[~2005-11-17 21:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-17 21:13 Jonathan Roewen
2005-11-17 21:47 ` Oliver Bandel
2005-11-17 21:57   ` Jonathan Roewen [this message]
2005-11-17 22:16   ` Damien Bobillot
2005-11-17 22:43     ` Daniel Bünzli
2005-11-17 22:55       ` Jonathan Roewen
2005-11-18  1:26         ` Vincenzo Ciancia
2005-11-18 10:04         ` [Caml-list] " Alessandro Baretta
2005-11-17 22:55       ` Damien Bobillot
2005-11-17 23:01 ` Vincenzo Ciancia
2005-11-17 23:49 ` [Caml-list] " Erik de Castro Lopo
2005-11-18  1:52   ` Grégory Guyomarc'h
2005-11-18  3:06   ` Brian Hurt
2005-11-18  3:29     ` Jonathan Roewen
2005-11-18 19:22     ` Ken Rose
2005-11-21  9:11       ` Sebastian Egner

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=ad8cfe7e0511171357j23b36f73n43c2ae9c682419ec@mail.gmail.com \
    --to=jonathan.roewen@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=oliver@first.in-berlin.de \
    /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).