From: Jeff Law <law@redhat.com>
To: Trevor Saunders <tbsaunde@tbsaunde.org>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [RFA] [PATCH] [PR tree-optimization/68619] Avoid direct cfg cleanups in tree-ssa-dom.c [1/3]
Date: Wed, 09 Dec 2015 00:44:00 -0000 [thread overview]
Message-ID: <56677982.1020706@redhat.com> (raw)
In-Reply-To: <20151208122340.GA17982@tsaunders-iceball.corp.tor1.mozilla.com>
On 12/08/2015 08:36 AM, Trevor Saunders wrote:
>
> Thinking about this more I wonder if we could move more of this into the
> dom walker, and skip calling before / after dom_children on unreachable
> blocks all together. That would seem to work for sccvn, but I'm not
> sure about what tree-ssa-dom.c is doing with the mark pushing and
> clearing.
Total brain lock, it hit when I got Richi's message, dumping it in the
walker itself is the obvious choice.
jeff
prev parent reply other threads:[~2015-12-09 0:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 6:15 Jeff Law
2015-12-08 14:23 ` Richard Biener
2015-12-08 14:27 ` Richard Biener
2015-12-09 8:31 ` Jeff Law
2015-12-09 10:45 ` Richard Biener
2015-12-08 23:00 ` Jeff Law
2015-12-08 15:36 ` Trevor Saunders
2015-12-09 0:44 ` Jeff Law [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=56677982.1020706@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=tbsaunde@tbsaunde.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).