From: Christophe TROESTLER <Christophe.Troestler@umh.ac.be>
To: xavier.leroy@inria.fr
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] 32 bit floats, SSE instructions
Date: Wed, 09 Jun 2004 19:58:51 +0200 (CEST) [thread overview]
Message-ID: <20040609.195851.23038890.Christophe.Troestler@umh.ac.be> (raw)
In-Reply-To: <20040609182602.D17538@pauillac.inria.fr>
On Wed, 9 Jun 2004, Xavier Leroy <xavier.leroy@inria.fr> wrote:
>
> I was about to post a long and detailed reply explaining the
> difference between computational types and storage types, why I
> think 32-bit floats might be useful as the latter but not at the
> former, quoting cycle counts from various processor manuals, mention
> what could conceivably be done in OCaml at minimal implementation
> costs, discuss SSE2 a bit, and generally answer the OP's initial
> questions. [...] Then I decided not to post.
Please consider to do it for those, like me, who always learn a lot
from this kind of posts.
Cheers,
ChriS
-------------------
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
next prev parent reply other threads:[~2004-06-09 17:58 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 17:15 Jon Harrop
2004-06-08 19:59 ` Brandon J. Van Every
2004-06-09 3:15 ` skaller
2004-06-09 4:08 ` Brian Hurt
2004-06-09 6:33 ` skaller
2004-06-09 9:12 ` [Caml-list] popular for being popular Brandon J. Van Every
2004-06-09 16:18 ` Brian Hurt
2004-06-09 19:08 ` Brandon J. Van Every
2004-06-09 16:26 ` [Caml-list] 32 bit floats, SSE instructions Xavier Leroy
2004-06-09 17:58 ` Christophe TROESTLER [this message]
2004-06-09 18:15 ` Daniel Ortmann
2004-06-09 18:52 ` Kenneth Knowles
2004-06-09 20:03 ` John Carr
2004-06-09 19:54 ` Brandon J. Van Every
-- strict thread matches above, loose matches on Subject: below --
2004-06-08 8:10 Ennals, Robert
2004-06-08 11:17 ` skaller
2004-06-08 17:42 ` John Carr
2004-06-09 16:13 ` Xavier Leroy
2004-06-07 11:13 Brandon J. Van Every
2004-06-07 11:32 ` Christophe TROESTLER
[not found] ` <20040607131717.GA12136@gaia.cc.gatech.edu>
2004-06-07 16:53 ` Christophe TROESTLER
2004-06-07 19:30 ` Brandon J. Van Every
2004-06-07 20:39 ` Nicolas Cannasse
2004-06-08 5:42 ` Brandon J. Van Every
2004-06-08 16:54 ` Jon Harrop
2004-06-08 20:50 ` Brandon J. Van Every
2004-06-09 3:19 ` skaller
2004-06-08 14:23 ` Keith Wansbrough
2004-06-10 14:43 ` David Brown
2004-06-10 15:20 ` Keith Wansbrough
2004-06-10 15:57 ` skaller
2004-06-10 16:23 ` Keith Wansbrough
2004-06-10 16:47 ` skaller
2004-06-10 19:46 ` Evan Martin
2004-06-07 21:00 ` Richard Jones
2004-06-07 21:42 ` Jon Harrop
2004-06-09 15:55 ` Richard Jones
2004-06-07 22:48 ` Chris Clearwater
2004-06-07 17:01 ` brogoff
2004-06-08 1:50 ` Brian Hurt
2004-06-08 5:27 ` Brandon J. Van Every
2004-06-08 15:05 ` Brian Hurt
2004-06-08 16:50 ` art yerkes
2004-06-08 17:10 ` Jon Harrop
2004-06-08 19:24 ` Brandon J. Van Every
2004-06-09 0:25 ` Jon Harrop
2004-06-09 1:33 ` Brandon J. Van Every
2004-06-09 3:04 ` Jon Harrop
2004-06-09 3:27 ` skaller
2004-06-09 14:21 ` Christophe TROESTLER
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=20040609.195851.23038890.Christophe.Troestler@umh.ac.be \
--to=christophe.troestler@umh.ac.be \
--cc=caml-list@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;
as well as URLs for NNTP newsgroup(s).