unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Re: CPS common subexpression elimination landed
Date: Tue, 08 Apr 2014 09:13:37 +0200	[thread overview]
Message-ID: <87ppksguou.fsf@pobox.com> (raw)
In-Reply-To: <87lhvhk2h6.fsf@pobox.com> (Andy Wingo's message of "Mon, 07 Apr 2014 09:44:53 +0200")

On Mon 07 Apr 2014 09:44, Andy Wingo <wingo@pobox.com> writes:

> The differences are these:

One more difference.  The old pass did a form of interprocedural CSE,
which was pretty neat.  The new pass does not do that.  Mostly the
reason it does not do so is to reduce complexity.  The other reason is
that the new pass runs after contification, so it sees bigger functions
than the old pass did, which had no way to understand contification.

Still, it's a limitation.  Oh well.

Andy
-- 
http://wingolog.org/



      reply	other threads:[~2014-04-08  7:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07  7:44 CPS common subexpression elimination landed Andy Wingo
2014-04-08  7:13 ` Andy Wingo [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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ppksguou.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).