From: art yerkes <ayerkes@speakeasy.net>
To: Brian Hurt <bhurt@spnz.org>
Cc: vanevery@indiegamedesign.com, caml-list@inria.fr
Subject: Re: [Caml-list] 32 bit floats, SSE instructions
Date: Tue, 8 Jun 2004 11:50:25 -0500 [thread overview]
Message-ID: <20040608115025.1dd9c993.ayerkes@speakeasy.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0406081002080.4243-100000@localhost.localdomain>
On Tue, 8 Jun 2004 10:05:12 -0500 (CDT)
Brian Hurt <bhurt@spnz.org> wrote:
> On Mon, 7 Jun 2004, Brandon J. Van Every wrote:
>
> > At the cost of inverting almost everyone's software architecture. This
> > is ridiculous / stupid in the real world. It's also baloney on
> > theoretical grounds: for just how many problems do you think it's worth
> > destrying memory coherence by putting structure elements very far apart
> > in memory? If you only want to do SoA "for some array length, then
> > start over," just how segmented did you think I wanted my programming
> > model to be?
> >
> > SoA might make sense if a language implementation did it totally behind
> > the scenes, presenting a seemingly AoS interface to programmers.
> > Exposing / locking into SoA is dumb, and yes, Intel is damn dumb. You
> > don't think they're dumb, look at their chips. They're good at fab and
> > marketing, they make lousy tack-on "kitchen sink" chips.
> >
On this topic, you can easily make a C-accessible array of unboxed 32-bit
floats using bigarray.
--
Hey, Adam Smith, keep your invisible hands to yourself!
-------------------
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-08 16:49 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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:28 ` [Caml-list] 3D graphics debate Brandon J. Van Every
2004-06-09 2:40 ` Jon Harrop
2004-06-09 8:09 ` Brandon J. Van Every
2004-06-09 1:33 ` [Caml-list] 32 bit floats, SSE instructions Brandon J. Van Every
2004-06-09 3:04 ` Jon Harrop
2004-06-09 8:33 ` [Caml-list] The multiresolution business model Brandon J. Van Every
2004-06-09 3:27 ` [Caml-list] 32 bit floats, SSE instructions skaller
2004-06-09 14:21 ` Christophe TROESTLER
2004-06-09 2:57 ` [Caml-list] RE: 3D Rendering pipeline Brian Hurt
2004-06-10 17:55 ` [Caml-list] Re: [Ocaml-lib-devel] " Nicolas Cannasse
2004-06-08 8:10 [Caml-list] 32 bit floats, SSE instructions Ennals, Robert
2004-06-08 11:17 ` skaller
2004-06-08 17:42 ` John Carr
2004-06-09 16:13 ` Xavier Leroy
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 16:26 ` Xavier Leroy
2004-06-09 17:58 ` Christophe TROESTLER
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
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=20040608115025.1dd9c993.ayerkes@speakeasy.net \
--to=ayerkes@speakeasy.net \
--cc=bhurt@spnz.org \
--cc=caml-list@inria.fr \
--cc=vanevery@indiegamedesign.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;
as well as URLs for NNTP newsgroup(s).