From: Richard Biener <rguenther@suse.de>
To: Tamar Christina <tamar.christina@arm.com>
Cc: gcc-patches@gcc.gnu.org, nd@arm.com, jlaw@ventanamicro.com
Subject: Re: [PATCH]middle-end: On emergency dumps finish the graph generation.
Date: Wed, 8 Mar 2023 07:22:11 +0000 (UTC) [thread overview]
Message-ID: <nycvar.YFH.7.77.849.2303080722050.18795@jbgna.fhfr.qr> (raw)
In-Reply-To: <patch-17094-tamar@arm.com>
On Tue, 7 Mar 2023, Tamar Christina wrote:
> Hi All,
>
> When doing an emergency dump the cfg output dumps are corrupted because the
> ending "}" is missing.
>
> Normally when the pass manager finishes it would call finish_graph_dump_file to
> produce this. This is called here because each pass can dump multiple digraphs.
>
> However during an emergency dump we only dump the current function and so after
> that is done we never go back to the pass manager.
>
> As such, we need to manually call finish_graph_dump_file in order to properly
> finish off graph generation.
>
> With this -ftree-dump-*-graph works properly during a crash dump.
>
> Bootstrapped Regtested on aarch64-none-linux-gnu and no issues.
>
> Ok for master?
OK.
> Thanks,
> Tamar
>
> gcc/ChangeLog:
>
> * passes.cc (emergency_dump_function): Finish graph generation.
>
> --- inline copy of patch --
> diff --git a/gcc/passes.cc b/gcc/passes.cc
> index 347214e81d0cfac05d9ba782db0eda1cdd7e9c87..38642a4010941b414a1ed1fd70a348778addbf60 100644
> --- a/gcc/passes.cc
> +++ b/gcc/passes.cc
> @@ -1845,6 +1845,13 @@ emergency_dump_function ()
> fprintf (dump_file, "\n\n\nEMERGENCY DUMP:\n\n");
> execute_function_dump (cfun, current_pass);
>
> + /* Normally the passmanager will close the graphs as a pass could be wanting
> + to print multiple digraphs. But during an emergency dump there can only be
> + one and we must finish the graph manually. */
> + if ((cfun->curr_properties & PROP_cfg)
> + && (dump_flags & TDF_GRAPH))
> + finish_graph_dump_file (dump_file_name);
> +
> if (symtab && current_pass->type == IPA_PASS)
> symtab->dump (dump_file);
> }
>
>
>
>
>
--
Richard Biener <rguenther@suse.de>
SUSE Software Solutions Germany GmbH, Frankenstrasse 146, 90461 Nuernberg,
Germany; GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman;
HRB 36809 (AG Nuernberg)
prev parent reply other threads:[~2023-03-08 7:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 17:38 Tamar Christina
2023-03-08 7:22 ` Richard Biener [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=nycvar.YFH.7.77.849.2303080722050.18795@jbgna.fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jlaw@ventanamicro.com \
--cc=nd@arm.com \
--cc=tamar.christina@arm.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).