From: Michel Christophe <tofm2@yahoo.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] architecture optimisation at compile time for ocaml 3.06
Date: 01 Jul 2003 17:30:45 +0200 [thread overview]
Message-ID: <1057073445.2794.10.camel@msi.ratatatator.com> (raw)
In-Reply-To: <200307011908.02487.snob@metalinkltd.com>
> > 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.
And it does fit, mine works fine, extremely fine. But... why not put
some cflags possibilities in it, so that one can enhance the performance
of his compiler on certain kinds of architecture..
> > 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.
yes, any processor specific optimization would be worth doing in my
opinion. I am not an ocaml expert, far from this...!! All I wanted was a
working compiler, I now have it, but every time I install a new soft on
my machine, i want it to run fast as a shark.
Even Linux kernel is achitecture optimized, so why not ocaml ?
note: this is just a suggestion, don't take it badly.
-------------------
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
prev parent reply other threads:[~2003-07-01 15:30 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
2003-07-01 15:30 ` Michel Christophe [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=1057073445.2794.10.camel@msi.ratatatator.com \
--to=tofm2@yahoo.fr \
--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;
as well as URLs for NNTP newsgroup(s).