caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Eray Ozkural <examachine@gmail.com>
To: Caml List <caml-list@inria.fr>
Subject: [Caml-list] Unboxing: how to do it best?
Date: Sat, 15 Jan 2011 14:02:11 +0200	[thread overview]
Message-ID: <AANLkTi=g2bny3VaSEOhYxEJRO_iGur365FgEsJe6d-_G@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 852 bytes --]

It's obvious that avoiding pointer chasing, improving locality and reducing
storage will in some cases improve performance considerably. I've found many
discussions about unboxing, but I haven't seen any solutions that would
satisfy high-performance-computing programmers, who would probably like to
have better (i.e. fine-grained) control over memory layout (unboxing double
arrays isn't enough). In C++ this is trivial, because C++ is just an
abstraction of assembly code. To cut it short,  could not we have basically
the same affordances of C++ in ocaml by annotating type definitions to
indicate where unboxing would be forced? Such annotations aren't a new idea
in programming languages, specifically HPF was based largely on parallel
storage annotations.

Regards,

-- 
Eray Ozkural, PhD candidate.  Comp. Sci. Dept., Bilkent University, Ankara

[-- Attachment #2: Type: text/html, Size: 952 bytes --]

             reply	other threads:[~2011-01-15 12:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-15 12:02 Eray Ozkural [this message]
2011-01-15 12:38 ` Guillaume Yziquel
2011-01-15 14:00   ` Eray Ozkural
2011-01-15 17:23     ` Guillaume Yziquel
2011-01-15 18:33       ` Eray Ozkural
2011-01-16 16:53         ` Jon Harrop
2011-01-18 23:49         ` Guillaume Yziquel
2011-01-15 12:41 ` bluestorm
2011-01-15 13:37   ` Eray Ozkural
2011-01-16 17:03 ` Jon Harrop

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='AANLkTi=g2bny3VaSEOhYxEJRO_iGur365FgEsJe6d-_G@mail.gmail.com' \
    --to=examachine@gmail.com \
    --cc=caml-list@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).