caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Mark Shinwell <mshinwell@janestreet.com>
To: Markus Mottl <markus.mottl@gmail.com>
Cc: OCaml List <caml-list@inria.fr>
Subject: Re: [Caml-list] CSE with FLambda?
Date: Tue, 21 Jun 2016 07:17:13 +0100	[thread overview]
Message-ID: <CAM3Ki76RV-Kqyg4HvPxGc6SVVqgg01Ee5CxbFwi4zSo2gBhg0A@mail.gmail.com> (raw)
In-Reply-To: <CAP_800osLpU4vGZ+TvsL0OEuB8pSHSdLjYhm_z_WB1K=pU6hfg@mail.gmail.com>

This doesn't happen at the moment.  We have it on our roadmap for
OCaml 4.05 (freeze around January 2017) to implement some form of pure
function application lifting and sharing, of which this is an example.
We also plan to consider introducing some notion of "function body"
(disentangling them from closures) so that we can automatically
deduplicate functions in general.

Mark

On 20 June 2016 at 16:37, Markus Mottl <markus.mottl@gmail.com> wrote:
> I haven't seen any reference to common subexpression elimination in
> the FLambda documentation.  Sometimes a functor may be applied to the
> exact same module in different parts of the code, and it may be
> cumbersome to factor out this application.
>
> Is or will FLambda be able to recognize such potential code
> duplication and perform CSE on functor applications with identical
> arguments?
>
> Regards,
> Markus
>
> --
> Markus Mottl        http://www.ocaml.info        markus.mottl@gmail.com
>
> --
> 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

      reply	other threads:[~2016-06-21  6:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-20 15:37 Markus Mottl
2016-06-21  6:17 ` Mark Shinwell [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=CAM3Ki76RV-Kqyg4HvPxGc6SVVqgg01Ee5CxbFwi4zSo2gBhg0A@mail.gmail.com \
    --to=mshinwell@janestreet.com \
    --cc=caml-list@inria.fr \
    --cc=markus.mottl@gmail.com \
    /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).