From: Tom de Vries <Tom_deVries@mentor.com>
To: Richard Biener <rguenther@suse.de>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, Jan Hubicka <hubicka@ucw.cz>
Subject: Re: [PATCH, PR70161] Fix fdump-ipa-all-graph
Date: Thu, 17 Mar 2016 11:16:00 -0000 [thread overview]
Message-ID: <56EA91DA.8070101@mentor.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1603151237080.15580@t29.fhfr.qr>
On 15/03/16 12:37, Richard Biener wrote:
> On Mon, 14 Mar 2016, Tom de Vries wrote:
>
>> Hi,
>>
>> this patch fixes PR70161, a 4.9/5/6 regression.
>>
>> Currently when using -fdump-ipa-all-graph, the compiler ICEs in
>> execute_function_dump when testing for pass->graph_dump_initialized, because
>> pass == NULL.
>>
>> The patch fixes:
>> - the ICE by setting the pass argument in the call to
>> execute_function_dump in execute_one_ipa_transform_pass
>> - a subsequent ICE (triggered with -fipa-pta) by saving, resetting and
>> restoring dump_file_name in cgraph_node::get_body, alongside the
>> saving and restoring of the dump_file variable.
>> - the duplicate edges in the subsequently generated dot file by
>> ensuring that execute_function_dump is called only once per function
>> per pass. [ Note that this bit also has an effect for the normal dump
>> files for the ipa passes with transform function. For those functions,
>> atm execute_function_dump is called both after execute and after
>> transform. With the patch, it's only called after transform. ]
>>
>> Bootstrapped and reg-tested on x86_64.
>>
>> OK for stage4?
>
> Ok.
All of the patch also OK for 4.9/5 branch?
[ The first 2 bits fix ICES. The last part fixes a duplicate edges
problem in the dot file, I'm not sure if that's needed in the release
branches. ]
Thanks,
- Tom
next prev parent reply other threads:[~2016-03-17 11:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 15:33 Tom de Vries
2016-03-15 11:37 ` Richard Biener
2016-03-17 11:16 ` Tom de Vries [this message]
2016-03-17 11:19 ` Richard Biener
2016-03-18 9:33 ` Tom de Vries
2016-03-18 9:45 ` Tom de Vries
2016-04-17 6:09 ` [PING, testsuite] Add dot-file scan to test-case Tom de Vries
2016-04-18 7:30 ` Richard Biener
2016-04-18 7:59 ` Tom de Vries
2016-04-18 8:40 ` 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=56EA91DA.8070101@mentor.com \
--to=tom_devries@mentor.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--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).