Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Vitaly Lugovsky <vsl@ontil.ihep.su>, caml-list@inria.fr
Subject: Re: Performance
Date: Tue, 18 Jul 2000 22:32:59 +0200	[thread overview]
Message-ID: <20000718223259.01177@pauillac.inria.fr> (raw)
In-Reply-To: <Pine.LNX.4.10.10007091656230.22814-100000@ontil.ihep.su>; from Vitaly Lugovsky on Sun, Jul 09, 2000 at 05:00:40PM +0400

>  What about some special platform-dependent tuning in native compilers?
> There is a great difference for 386/586/686/686MMX, and the same for
> sparc/ssparc/usparc...

The ocaml native compiler is a bit too simple-minded to schedule
optimally for e.g. the 586 or the latest Sparcs, which requires quite
a lot of processor-specific knowledge indeed.

Concerning the x86 family, I modified some of the compiler idioms over
time to adapt to the "dominant" processor of the time.  (E.g. avoid
AGI stalls for the 486; avoid movzbl for the Pentium; etc.)  The 686
family (Pentium Pro/II/III), which is dominant nowadays, does so much
work "behind the scene" that those tweaks are no longer needed and
ocamlopt generates pretty much the most straightforward instruction
sequences.

As for the Sparc code generator, it is maintained but not actively
developed.  The Sparc is a dying platform, at least here at INRIA
(the last we bought in our group was in 1993...), so we're not
investing big efforts in it.

>  And, can anybody do a benchmark for bytecode performance on Itanium
> and Alpha? I think, it'll be a good test for a new architecture...

I could do it, but then Intel would have to kill me :-)  Like all
happy fews that have access to a prototype Itanium machine, I had to
agree not to do any benchmarking on this machine.  Apparently, the
prototype Itaniums don't implement all the performance tricks of the final
Itanium processor, and Intel doesn't want to get bad press because of
this.

- Xavier Leroy



      reply	other threads:[~2000-07-19 15:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-09 13:00 Performance Vitaly Lugovsky
2000-07-18 20:32 ` Xavier Leroy [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=20000718223259.01177@pauillac.inria.fr \
    --to=xavier.leroy@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=vsl@ontil.ihep.su \
    /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