From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Christopher Jeris <cjeris@math.mit.edu>, caml-list@inria.fr
Subject: Re: [caml] Closures and efficiency
Date: Fri, 29 Oct 1999 10:56:29 +0200 [thread overview]
Message-ID: <19991029105629.43047@pauillac.inria.fr> (raw)
In-Reply-To: <Pine.SUN.4.20.9910261748340.6977-100000@schauder.mit.edu>; from Christopher Jeris on Tue, Oct 26, 1999 at 06:06:28PM -0400
> Here's the nub of my question. In a typical synth architecture there are
> very many parameters which take values 0..127. If I had a function
>
> int_subrange_encoder: int -> int -> param_value -> bytestring
>
> which took the bounds of a subrange and generated an encoder function for
> values of that subrange, and then in a voice-architecture description I
> had a list of very many records each of which contained an entry
>
> int_subrange_encoder 0 127
>
> would I suddenly have six million little closures, or would the compiler
> do common-subexpression elimination on them ?
As of now, the compiler doesn't do any common subexpression
elimination. Notice that CSE over function applications is hard,
because the compiler must make sure that the function has no side-effects.
E.g. assume your function int_subrange_encoder prints something after
receiving its first two arguments:
let int_subrange_encoder lo hi =
print_string "subrange_encoder was here!";
fun param -> ...
Then, CSE would be incorrect.
An easy thing to do is to let-bind the partial applications that
occur frequently:
let int_encoder = int_subrange_encoder 0 127
and then use "int_encoder" instead of "int_subrange_encoder 0 127"
in your descriptions.
Hope this helps,
- Xavier Leroy
next prev parent reply other threads:[~1999-10-29 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-26 22:06 Christopher Jeris
1999-10-29 8:56 ` Xavier Leroy [this message]
1999-10-29 9:39 ` Francois Pottier
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=19991029105629.43047@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=cjeris@math.mit.edu \
/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).