From: skaller <skaller@users.sourceforge.net>
To: Hal Daume III <hdaume@ISI.EDU>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] bigarrays much lower than normal ones
Date: 01 Nov 2004 11:05:41 +1100 [thread overview]
Message-ID: <1099267540.15048.5.camel@pelican.wigram> (raw)
In-Reply-To: <Pine.LNX.4.44.0410310750180.22156-100000@albini.isi.edu>
On Mon, 2004-11-01 at 03:05, Hal Daume III wrote:
> I'm also really shocked that the 32 bit float bigarrays are slower than
> the 64 bit ones!
IEEE hardware loads/saves 64 bit and converts internally to 80 bit.
32 bit requires extra conversions. OTOH you might save on memory
and gain some performance wrt caches.
--
John Skaller, mailto:skaller@users.sf.net
voice: 061-2-9660-0850,
snail: PO BOX 401 Glebe NSW 2037 Australia
Checkout the Felix programming language http://felix.sf.net
prev parent reply other threads:[~2004-11-01 0:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-31 16:05 Hal Daume III
2004-10-31 17:26 ` [Caml-list] " John Prevost
2004-10-31 17:41 ` malc
2004-11-01 0:05 ` skaller [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=1099267540.15048.5.camel@pelican.wigram \
--to=skaller@users.sourceforge.net \
--cc=caml-list@yquem.inria.fr \
--cc=hdaume@ISI.EDU \
/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).