caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Xavier Leroy <xavier.leroy@inria.fr>
To: Richard Jones <rich@annexia.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml not automatically specialising a polymorphic function
Date: Wed, 25 Jun 2003 17:36:59 +0200	[thread overview]
Message-ID: <20030625173659.B22658@pauillac.inria.fr> (raw)
In-Reply-To: <20030625150535.GA15972@redhat.com>; from rich@annexia.org on Wed, Jun 25, 2003 at 04:05:35PM +0100

> - max3.ml ------------------------------------------------------------
> let max a b =
>   if a > b then a else b
> in
> 
> print_int (max 2 3);;
> ----------------------------------------------------------------------
> 
> Looking at the assembler, OCaml doesn't work out that "max" has type
> max : int -> int -> int

Yes, because it has type 'a -> 'a -> 'a according to the ML typing rules...
But if you help OCaml with a type constraint, you'll get the more
efficient code that you expect:

  let max (a:int) (b:int) = ...

> , and so it generates very inefficient
> code. This is a bit surprising because (I think) max can't be called
> from outside the module, and the one place where it is called
> specifies the type.
> So I'm guessing here that OCaml doesn't really optimize across
> functions?

You're correct that OCaml doesn't do type specialization for
user-defined functions (only for some predefined operations like ">"). 
It does perform some inter-function optimizations such as function
inlining and known call optimizations.

- Xavier Leroy

-------------------
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


      reply	other threads:[~2003-06-25 15:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-25 15:05 Richard Jones
2003-06-25 15:36 ` Xavier Leroy [this message]

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=20030625173659.B22658@pauillac.inria.fr \
    --to=xavier.leroy@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=rich@annexia.org \
    /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).