From: luc.maranget@inria.fr (Luc Maranget)
To: Gerd Stolpmann <info@gerd-stolpmann.de>
Cc: Diego Olivier FERNANDEZ PONS <diego.fernandez_pons@etu.upmc.fr>,
caml-list@inria.fr
Subject: Re: [Caml-list] Why + vs +. but "fake" parametric polymorphism for <
Date: Fri, 13 Oct 2006 16:16:21 +0200 [thread overview]
Message-ID: <20061013141621.GD10977@yquem.inria.fr> (raw)
In-Reply-To: <1160747618.16545.24.camel@localhost.localdomain>
>
> Of course, you may ask why Ocaml's inlining feature isn't clever enough
> to do late specialisation, at least of functions that can be inlined. I
> don't know.
>
> Gerd
> --
Technically, the ocamlc and ocamlopt compilers share a common
front end that performs the specialization (on the so-called
typed syntax, if I remember well).
By design, both compilers have a lot common.
Only the ocamlopt compiler performs inlining, on a later
internal representation of code.
As to re-performing specialisation in ocamlopt back-end,
precise types are lost there, I am afraid. This may be by design.
--Luc
next prev parent reply other threads:[~2006-10-13 14:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 5:18 Carlos Pita
2006-10-12 5:45 ` [Caml-list] " Jacques Garrigue
2006-10-12 5:58 ` Carlos Pita
2006-10-12 6:08 ` Jonathan Roewen
[not found] ` <452DF46C.802@fmf.uni-lj.si>
2006-10-12 14:26 ` Carlos Pita
2006-10-13 11:56 ` Diego Olivier FERNANDEZ PONS
2006-10-13 12:14 ` Gerd Stolpmann
2006-10-13 12:46 ` Diego Olivier FERNANDEZ PONS
2006-10-13 13:01 ` Luc Maranget
2006-10-13 13:15 ` Diego Olivier FERNANDEZ PONS
2006-10-13 13:15 ` skaller
2006-10-13 13:36 ` Luc Maranget
2006-10-13 13:53 ` Gerd Stolpmann
2006-10-13 14:16 ` Luc Maranget [this message]
2006-10-12 5:19 Carlos Pita
2006-10-12 5:41 ` [Caml-list] " Carlos Pita
2006-10-12 5:49 ` Basile STARYNKEVITCH
2006-10-12 5:53 ` Jonathan Roewen
2006-10-12 6:10 ` Carlos Pita
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=20061013141621.GD10977@yquem.inria.fr \
--to=luc.maranget@inria.fr \
--cc=caml-list@inria.fr \
--cc=diego.fernandez_pons@etu.upmc.fr \
--cc=info@gerd-stolpmann.de \
/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).