From: Ville-Pertti Keinonen <will@exomi.com>
To: John Carr <jfc@MIT.EDU>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Function Inlining
Date: Wed, 03 Aug 2005 10:16:12 +0300 [thread overview]
Message-ID: <42F06F3C.6060508@exomi.com> (raw)
In-Reply-To: <200508021503.j72F35hR011108@all-night-tool.mit.edu>
John Carr wrote:
> the assembly code would look like (with tag values omitted for clarity):
...
That definitely looks good.
> This solves the stack overflow problem. I'm not convinced that
> the asmcomp phase of the compiler is the right place to do this
> optimization. Perhaps it should be moved to the intermediate
> phase where the top level module optimization is done now.
One problem with this might be that you don't even have any kind of
constant folding done at that point (I assume you're referring to the
transl* phase), so you'd either have to duplicate that functionality or
limit it to simple constants.
prev parent reply other threads:[~2005-08-03 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-01 21:24 Jonathan Bryant
2005-08-02 6:44 ` [Caml-list] " Ville-Pertti Keinonen
2005-08-02 15:03 ` John Carr
2005-08-03 7:16 ` Ville-Pertti Keinonen [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=42F06F3C.6060508@exomi.com \
--to=will@exomi.com \
--cc=caml-list@inria.fr \
--cc=jfc@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).