From: Nickolay Kolchin-Semyonov <snob@metalinkltd.com>
To: Xavier Leroy <xavier.leroy@inria.fr>, Christophe Michel <tofm2@yahoo.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] architecture optimisation at compile time for ocaml 3.06
Date: Tue, 1 Jul 2003 19:08:02 +0400 [thread overview]
Message-ID: <200307011908.02487.snob@metalinkltd.com> (raw)
In-Reply-To: <20030701152320.B14262@pauillac.inria.fr>
On Tuesday 01 July 2003 17:23, Xavier Leroy wrote:
> > my system relies on an athlon XP2000+ and I would like to take
>
> The native-code OCaml compiler has only one code generator for the
> whole IA32 family. This code generator is called "i386" for
> historical reasons, but it is not particulary optimized for the Intel
> 386 processor. Actually, the generated code is targeted for efficient
> execution on the PPro-PII-PIII family, and appears to fit the Athlon
> quite well too. The next release will include a few P4-specific
> tricks that do not decrease performance on other processors.
What about "cmov" support? This is not P4 specific, this command present for
extremely long time.
>
> > can anyone help me in optimizing source for athlon ??
>
> No :-) Quite frankly, given the subset of the IA32 instruction set
> that OCaml generates, I can't see any Athlon-specific optimizations
> that would be worth doing.
>
3DNow, cache control. This are just first thoughts.
Nickolay
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-07-01 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-01 9:07 Christophe Michel
2003-07-01 13:23 ` Xavier Leroy
2003-07-01 15:08 ` Nickolay Kolchin-Semyonov [this message]
2003-07-01 15:30 ` Michel Christophe
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=200307011908.02487.snob@metalinkltd.com \
--to=snob@metalinkltd.com \
--cc=caml-list@inria.fr \
--cc=tofm2@yahoo.fr \
--cc=xavier.leroy@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;
as well as URLs for NNTP newsgroup(s).