From: Diego Novillo <dnovillo@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Richard Henderson <rth@redhat.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix PR tree-optimization/17724
Date: Fri, 08 Oct 2004 23:48:00 -0000 [thread overview]
Message-ID: <1097278087.1021.8.camel@localhost.localdomain> (raw)
In-Reply-To: <20041007200445.GN31909@devserv.devel.redhat.com>
On Thu, 2004-10-07 at 16:04, Jakub Jelinek wrote:
> The third one recomputes dominators (and post-dominators) of neighbours
> of unreachable basic blocks after they are deleted by
> delete_unreachable_blocks.
>
I like this one. It looks OK and safe, so let's go with it.
Thanks. Diego.
next prev parent reply other threads:[~2004-10-08 23:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 20:13 Jakub Jelinek
2004-10-07 22:16 ` Kazu Hirata
2004-10-08 7:05 ` Jakub Jelinek
2004-10-08 19:32 ` Jeffrey A Law
2004-10-08 20:25 ` Andrew Pinski
2004-10-08 23:48 ` Diego Novillo [this message]
2004-10-09 8:24 ` Zdenek Dvorak
[not found] <20041009082440.GB22455@atrey.karlin.mff.cuni.cz>
2004-10-09 9:23 ` Zdenek Dvorak
-- strict thread matches above, loose matches on Subject: below --
2004-09-30 1:05 Jakub Jelinek
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=1097278087.1021.8.camel@localhost.localdomain \
--to=dnovillo@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=rth@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).