Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Michal Moskal <malekith@pld-linux.org>
To: Xavier Leroy <xavier.leroy@inria.fr>
Cc: caml-list@pauillac.inria.fr
Subject: Re: [Caml-list] Performance problem
Date: Thu, 15 May 2003 12:53:21 +0200	[thread overview]
Message-ID: <20030515105321.GA6096@roke.freak> (raw)
In-Reply-To: <20030515095751.A5384@pauillac.inria.fr>

On Thu, May 15, 2003 at 09:57:51AM +0200, Xavier Leroy wrote:
> > > 2) there are no problems using bytecode :
> > >      0.3s using bytecode
> > >      23s  using native
> 
> This I doubt very much, and indeed a quick test shows that bytecode
> and native take exactly the same time.  This isn't surprising:
> since 99% of the time is spent is the regexp engine, and this engine
> is in C, it runs at the same speed in bytecode and in native-code.

I have no idea *why* but here (Linux, x86), using ocamlc and ocamlopt
3.06, I get exactly the same timings (i.e. 0.44s for bytecode and 21.91s
for native code). No special options (like -p or -g) were used for
compilation.

Does the bytecode and nativecode use *exectly* the same C engine (i.e.
maybe one is compiled with different options (like -fpic -O2 or
someting) ?)

-- 
: Michal Moskal :: http://www.kernel.pl/~malekith : GCS {C,UL}++++$ a? !tv
: PLD Linux ::::::::: Wroclaw University, CS Dept : {E-,w}-- {b++,e}>+++ h

-------------------
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


  reply	other threads:[~2003-05-15 10:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14 21:03 Matt Gushee
2003-05-14 22:13 ` Ville-Pertti Keinonen
     [not found]   ` <20030514223956.GB27927@swordfish>
2003-05-14 22:41     ` Matt Gushee
2003-05-15  7:57       ` Xavier Leroy
2003-05-15 10:53         ` Michal Moskal [this message]
2003-05-14 23:13   ` Matt Gushee

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=20030515105321.GA6096@roke.freak \
    --to=malekith@pld-linux.org \
    --cc=caml-list@pauillac.inria.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