From: nr@eecs.harvard.edu (Norman Ramsey)
To: caml-list@inria.fr
Subject: [Caml-list] implementing bit vectors in OCaml
Date: Sun, 1 Jun 2003 13:03:17 -0400 (EDT) [thread overview]
Message-ID: <20030601170317.002EF12F9CE@flatcoat.eecs.harvard.edu> (raw)
We have a program that is spending a lot of time in set operations,
and we're thinking of trying an imperative implementation based on bit vectors.
I would hope that the basis of such an implementation would be an array
of native integers, but on scrutinizing the manual (espeically the chapter
on interfacing to C), I have concluded that such a thing is not possible.
Our choices appear to be
* An array of native integers, which will be implemented as an array
of pointers to native integers, because integers are boxed.
* An array of tagged integers, which will be less efficient as
dividing by 31 is more expensive than shifting.
How would the gurus recommend that we proceed? Is there a better,
still efficient data structure for a set of small integers?
Could the compiler gods be persuaded to provide unboxed
representations for arrays of untagged integers, as is already done
for `float array'?
Norman
-------------------
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 reply other threads:[~2003-06-01 17:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-01 17:03 Norman Ramsey [this message]
2003-06-01 17:50 ` Ville-Pertti Keinonen
2003-06-02 8:21 ` Diego Olivier Fernandez Pons
2003-06-02 8:54 ` Hendrik Tews
2003-06-02 8:59 ` Claude Marche
2003-06-02 9:26 ` Xavier Leroy
2003-06-02 10:11 ` Marcin 'Qrczak' Kowalczyk
2003-06-02 10:10 ` Fabrice Le Fessant
2003-06-02 13:29 Gregory Morrisett
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=20030601170317.002EF12F9CE@flatcoat.eecs.harvard.edu \
--to=nr@eecs.harvard.edu \
--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