From: wakita@is.titech.ac.jp
To: aheitner@andrew.cmu.edu
Cc: Xavier.Leroy@inria.fr, vsl@ontil.ihep.su, frisch@clipper.ens.fr,
williamc@paneris.org, caml-list@inria.fr,
web-caml@quatramaran.ens.fr
Subject: Re: [Caml-list] Web Development with OCaml
Date: Mon, 16 Jul 2001 17:23:15 +0900 (JST) [thread overview]
Message-ID: <20010716.172315.00455888.wakita@is.titech.ac.jp> (raw)
In-Reply-To: <20010715140351.B20044@andrew.cmu.edu>
i'm sorry that my comment is off the topic of web development...
A few months ago, I ran the Fibonacci test for gcc 2.95 and ocamlopt
on the Intel platform and saw the similar result; I was not interested
in PIC at the moment. First, I thought the difference was due to
inlining done by the ocamlopt but it was not the case for Fibonacci
function. Comparison of the assembly code produced by the both
compiler suggests that the difference is due primariry to the fact
that gcc does not optimize enough argument passing to functions.
Ken Wakita
Tokyo Institute of Technology
In message (<20010715140351.B20044@andrew.cmu.edu>)
from Ari Heitner <aheitner@andrew.cmu.edu>,
talking about "Re: [Caml-list] Web Development with OCaml",
on Sun, 15 Jul 2001 14:03:51 -0400
> I've definitely seen Java behave slowly. But today I did a dead-simple test
> (designed to avoid all the Java weaknesses): a recursive fib, and got
> interesting results:
> - Java was a touch faster than gcc (~10% penalty for not making the call
> "static")
> - gcc (2.95.4) was ~20% slower for pic. I seem to recall gcc 3.0 being
> maybe 10% faster, tho it may be quite a bit faster on less moronic code
> (i've heard up to 40%). but this is a moronic measure that only leans
> on function-call cost -- in real code it should be much less noticeable.
> no one seems to complain about either using shared libraries, or (to
> be like the java servlet arch below) explicitly loading code via dlopen.
> - ocaml is about 40% faster than java/gcc
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-07-16 8:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-10 0:01 Jimmie Houchin
2001-07-10 7:10 ` Jean-Christophe Filliatre
2001-07-10 7:15 ` Tom Hirschowitz
2001-07-10 8:19 ` David Mentre
2001-07-10 9:38 ` Alain Frisch
2001-07-11 5:49 ` Jimmie Houchin
2001-07-11 6:03 ` Alexander V. Voinov
2001-07-11 14:47 ` Jimmie Houchin
2001-07-12 1:58 ` John Max Skaller
2001-07-11 6:19 ` Alain Frisch
2001-07-11 9:09 ` Samuel Heriard Dubreuil
2001-07-11 14:11 ` Jimmie Houchin
2001-07-11 15:35 ` Francois Rouaix
2001-07-11 20:44 ` Gerd Stolpmann
2001-07-12 2:32 ` Jimmie Houchin
2001-07-13 5:37 ` William Chesters
2001-07-13 10:29 ` Alain Frisch
2001-07-13 11:16 ` Vitaly Lugovsky
2001-07-13 14:04 ` Xavier Leroy
2001-07-13 17:08 ` [web-caml] " Vitaly Lugovsky
2001-07-15 18:03 ` Ari Heitner
2001-07-15 20:19 ` Gerd Stolpmann
2001-07-16 8:23 ` wakita [this message]
2001-07-17 16:18 ` John Max Skaller
2001-07-17 18:50 ` Ari Heitner
2001-07-18 22:24 ` John Max Skaller
2001-07-13 16:12 ` Lyn A Headley
2001-07-13 17:50 ` William Chesters
2001-07-13 16:51 ` Miles Egan
2001-07-13 18:12 ` Jimmie Houchin
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=20010716.172315.00455888.wakita@is.titech.ac.jp \
--to=wakita@is.titech.ac.jp \
--cc=Xavier.Leroy@inria.fr \
--cc=aheitner@andrew.cmu.edu \
--cc=caml-list@inria.fr \
--cc=frisch@clipper.ens.fr \
--cc=vsl@ontil.ihep.su \
--cc=web-caml@quatramaran.ens.fr \
--cc=williamc@paneris.org \
/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