> 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