From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Re: 32- and 64-bit performance
Date: Thu, 31 Mar 2005 19:40:18 +0100 [thread overview]
Message-ID: <200503311940.18701.jon@ffconsultancy.com> (raw)
In-Reply-To: <871x9vzwk7.fsf-monnier+gmane.comp.lang.caml.inria@gnu.org>
On Thursday 31 March 2005 16:05, Stefan Monnier wrote:
> > I just bought a new Athlon 64 laptop and installed 32- and 64-bit Debian.
> > Here are some timings, showing the performance change when moving from
> > 32- to 64-bit using ocamlopt (3.08.2) and g++ (3.4.4):
>
> Is there a GNU/Linux (and OCaml) mode supporting the half-way case where
> you use the new amd64 registers but still stay with 32bit pointers?
> That should fix the one case where the amd64 mode is slower because of the
> extra memory use.
I do not believe there is such a mode, no. I'm not entirely sure how this
could work but I'm quite happy to take a performance hit in a few programs.
Particularly because arrays are so much more useful now. :-)
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
Objective CAML for Scientists
http://www.ffconsultancy.com/products/ocaml_for_scientists
next prev parent reply other threads:[~2005-03-31 18:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-30 2:40 Jon Harrop
2005-03-30 7:46 ` [Caml-list] " Alex Baretta
2005-03-30 8:00 ` Ville-Pertti Keinonen
2005-03-30 8:41 ` Alex Baretta
2005-03-30 9:01 ` Ville-Pertti Keinonen
2005-03-30 12:53 ` Jon Harrop
2005-03-30 14:34 ` Ville-Pertti Keinonen
2005-03-30 8:10 ` Robert Roessler
2005-03-30 8:11 ` Alexander S. Usov
2005-03-30 13:46 ` Eijiro Sumii
2005-03-31 13:42 ` Jon Harrop
2005-03-31 15:05 ` Stefan Monnier
2005-03-31 18:40 ` Jon Harrop [this message]
2005-03-31 22:41 ` [Caml-list] " Richard Jones
2005-04-02 20:23 ` Stefan Monnier
2005-04-02 20:50 ` [Caml-list] " David Brown
2005-04-03 10:01 ` Ville-Pertti Keinonen
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=200503311940.18701.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--cc=caml-list@yquem.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).