From: Robert Roessler <roessler@rftp.com>
To: Jon Harrop <jon@ffconsultancy.com>, Caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] x86 vs AMD64 OCaml compiler performance
Date: Wed, 06 Jul 2005 10:16:24 -0700 [thread overview]
Message-ID: <42CC11E8.8040505@rftp.com> (raw)
In-Reply-To: <200507060353.29648.jon@ffconsultancy.com>
Jon Harrop wrote:
> I just timed recompilation of my latest project to both byte code and native
> code on both 900MHz Athlon t-bird and 800MHz Athlon64. To my suprise,
> compilation to native code takes roughly the same amount of time on both
> computers but compilation to byte code is slightly faster (1m18 vs 1m40) on
> x86 but vastly faster (21s vs 1m50) on AMD64.
Ummm... do you mean "1800MHz" or "1.8GHz" for the Athlon64? :)
Robert Roessler
roessler@rftp.com
http://www.rftp.com
next prev parent reply other threads:[~2005-07-06 17:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 2:53 Jon Harrop
2005-07-06 6:44 ` [Caml-list] " Florian Hars
2005-07-06 16:20 ` Jon Harrop
2005-07-06 17:16 ` Robert Roessler [this message]
2005-07-06 17:31 ` Jon Harrop
2005-07-06 19:18 ` Christopher Campbell
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=42CC11E8.8040505@rftp.com \
--to=roessler@rftp.com \
--cc=caml-list@inria.fr \
--cc=jon@ffconsultancy.com \
/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