Version française
Home     About     Download     Resources     Contact us    

This site is updated infrequently. For up-to-date information, please visit the new OCaml website at

Browse thread
[Caml-list] Bigarray is a pig
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: Brandon J. Van Every <vanevery@i...>
Subject: RE: [Caml-list] Bigarray is a pig
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

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 Archives:
Bug reports: FAQ:
Beginner's list: