Re: [Caml-list] Ocaml optimizer pitfalls & work-arounds

[Gabriel Scherer <gabriel.scherer@gmail.com>]

> the min, max issues can be avoided without much trouble by using
> specialized comparison, as provided in standard library extensions.

Note that min/max are already optimized from generic to specialized
when the type information is known at type-checking time. (It used to
be the case that only fully applied calls were optimized, this was
improved by Frédéric Bour to extend to non-applied primitives in 4.03
(eg. "let eq : int -> int -> _ = (=)"). That does not work when those
functions are used inside a functor body at an abstract type (which is
when we want inlining and specialization to interact better), but
there neither do Float.equal or Int.compare.

On Thu, Jan 19, 2017 at 12:20 PM, Nils Becker
<nils.becker@bioquant.uni-heidelberg.de> wrote:
> a while ago there was a proposal for deprecating the specialized
> treatment of float arrays, which was not accepted iirc. it seems that
> the slowdown of all Array.get calls is quite a high price to pay. what
> do we gain from the float array specialization? (honest question - i
> don't have a good understanding)
>
> the min, max issues can be avoided without much trouble by using
> specialized comparison, as provided in standard library extensions.
>
> n.
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs