From: "H.J. Lu" <hjl.tools@gmail.com>
To: Richard Biener <rguenther@suse.de>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix PR66794
Date: Wed, 08 Jul 2015 14:53:00 -0000 [thread overview]
Message-ID: <CAMe9rOo9vi4m18G9xofqUmVxEjRUASv60YJF4pQntgawpJyc8w@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1507081345060.9923@zhemvz.fhfr.qr>
On Wed, Jul 8, 2015 at 4:46 AM, Richard Biener <rguenther@suse.de> wrote:
>
> Passes do not expect post-dominators being around and thus forget
> to invalidate them properly. Thus passes computing them have to
> free them. The patch fixes path-isolation and adds an assert so
> this doesn't happen again.
>
> Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to trunk.
>
> Richard.
>
> 2015-07-08 Richard Biener <rguenther@suse.de>
>
> PR tree-optimization/66794
> * passes.c (execute_function_todo): Assert that post-dominators
> are not computed.
> * gimple-ssa-isolate-paths.c (gimple_ssa_isolate_erroneous_paths):
> Free post-dominators.
>
This caused:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66807
--
H.J.
next prev parent reply other threads:[~2015-07-08 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 11:46 Richard Biener
2015-07-08 14:53 ` H.J. Lu [this message]
2015-07-09 7:46 ` Richard Biener
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=CAMe9rOo9vi4m18G9xofqUmVxEjRUASv60YJF4pQntgawpJyc8w@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).