From: "Brandon J. Van Every" <vanevery@indiegamedesign.com>
To: "caml" <caml-list@inria.fr>
Subject: RE: [Caml-list] Bigarray is a pig
Date: Sat, 24 Jul 2004 02:07:16 -0700 [thread overview]
Message-ID: <OOEALCJCKEBJBIJHCNJDMEJDHFAB.vanevery@indiegamedesign.com> (raw)
In-Reply-To: <20040723.230533.104027451.oandrieu@nerim.net>
Olivier Andrieu wrote:
> "Brand*n wrote:
> > I have been looking at the sources of the Bigarray implementation.
> > I am chagrined to discover that not only does Bigarray cost a
> > function call per array element access,
>
> No. Not always: when the type of the array is completely known to the
> compiler at the point the element is accessed, ocamlopt will access
> the element directly, without using the generic C function.
You are saying that even though Bigarray declares its array element
access functions as EXTERN, and implements them in C code, that ocamlopt
ignores this and does something else? Using some completely different
source code, perhaps? (And where is that code?)
Would ocamlopt generally perform such tricks for C functions declared
EXTERN? How?
Cheers, www.indiegamedesign.com
Brand*n Van Every S*attle, WA
Praise Be to the caml-list Bayesian filter! It blesseth
my postings, it is evil crap! evil crap! Bigarray!
Unboxed! Overhead! Wondering! chant chant chant...
-------------------
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-07-24 8:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 20:36 Brandon J. Van Every
2004-07-23 21:05 ` Brian Hurt
2004-07-24 9:49 ` Brandon J. Van Every
2004-07-23 21:05 ` Olivier Andrieu
2004-07-24 9:07 ` Brandon J. Van Every [this message]
2004-07-24 9:59 ` Marcin 'Qrczak' Kowalczyk
2004-07-25 9:09 ` David McClain
2004-07-24 10:39 ` Markus Mottl
2004-07-23 21:45 ` David McClain
2004-07-23 22:01 ` David McClain
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=OOEALCJCKEBJBIJHCNJDMEJDHFAB.vanevery@indiegamedesign.com \
--to=vanevery@indiegamedesign.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