From: Jeff Law <law@redhat.com>
To: Tom de Vries <Tom_deVries@mentor.com>,
"gcc-patches@gnu.org" <gcc-patches@gnu.org>
Subject: Re: [PATCH] Check no unreachable blocks in inverted_post_order_compute
Date: Mon, 12 Oct 2015 20:34:00 -0000 [thread overview]
Message-ID: <561C1969.3000801@redhat.com> (raw)
In-Reply-To: <561BB14D.9080309@mentor.com>
On 10/12/2015 07:10 AM, Tom de Vries wrote:
> Hi,
>
> in the header comment of function inverted_post_order_compute in
> cfganal.c we find:
> ...
> This function assumes that all blocks in the CFG are reachable
> from the ENTRY (but not necessarily from EXIT).
> ...
>
> This patch checks that there are indeed no unreachable blocks when
> calling inverted_post_order_compute.
>
> OK for trunk if bootstrap/regtest succeeds?
Yes. I won't queue it behind Mikhail's changes. Consider yourself
lucky :-)
jeff
prev parent reply other threads:[~2015-10-12 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 13:11 Tom de Vries
2015-10-12 20:34 ` 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=561C1969.3000801@redhat.com \
--to=law@redhat.com \
--cc=Tom_deVries@mentor.com \
--cc=gcc-patches@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).