From: Richard Biener <richard.guenther@gmail.com>
To: Eugene Rozenfeld <Eugene.Rozenfeld@microsoft.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][PUSHED] Fix cfg maintenance after inlining in AutoFDO
Date: Tue, 9 May 2023 08:40:29 +0200 [thread overview]
Message-ID: <CAFiYyc2=zNZ6yYFY96+c8ToAKBAm-_QBUFoSFPFfkbrCR24Vuw@mail.gmail.com> (raw)
In-Reply-To: <DS7PR21MB34793E5E1EA2C050CB45B2A691719@DS7PR21MB3479.namprd21.prod.outlook.com>
On Tue, May 9, 2023 at 12:27 AM Eugene Rozenfeld via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> Todo from early_inliner needs to be propagated so that
> cleanup_tree_cfg () is called if necessary.
>
> This bug was causing an assert in get_loop_body during
> ipa-sra in autoprofiledbootstrap build since loops weren't
> fixed up and one of the loops had num_nodes set to 0.
>
> Tested on x86_64-pc-linux-gnu.
>
> gcc/ChangeLog:
>
> * auto-profile.cc (auto_profile): Check todo from early_inline
> to see if cleanup_tree_vfg needs to be called.
_cfg
> (early_inline): Return todo from early_inliner.
> ---
> gcc/auto-profile.cc | 21 ++++++++++++---------
> 1 file changed, 12 insertions(+), 9 deletions(-)
>
> diff --git a/gcc/auto-profile.cc b/gcc/auto-profile.cc
> index 360c42c4b89..e3af3555e75 100644
> --- a/gcc/auto-profile.cc
> +++ b/gcc/auto-profile.cc
> @@ -1589,13 +1589,14 @@ afdo_annotate_cfg (const stmt_set &promoted_stmts)
>
> /* Wrapper function to invoke early inliner. */
>
> -static void
> +static unsigned int
> early_inline ()
> {
> compute_fn_summary (cgraph_node::get (current_function_decl), true);
> - unsigned todo = early_inliner (cfun);
> + unsigned int todo = early_inliner (cfun);
> if (todo & TODO_update_ssa_any)
> update_ssa (TODO_update_ssa);
> + return todo;
> }
>
> /* Use AutoFDO profile to annoate the control flow graph.
> @@ -1651,20 +1652,22 @@ auto_profile (void)
> function before annotation, so the profile inside bar@loc_foo2
> will be useful. */
> autofdo::stmt_set promoted_stmts;
> + unsigned int todo = 0;
> for (int i = 0; i < 10; i++)
> {
> - if (!flag_value_profile_transformations
> - || !autofdo::afdo_vpt_for_early_inline (&promoted_stmts))
> - break;
> - early_inline ();
> + if (!flag_value_profile_transformations
> + || !autofdo::afdo_vpt_for_early_inline (&promoted_stmts))
> + break;
> + todo |= early_inline ();
> }
>
> - early_inline ();
> + todo |= early_inline ();
> autofdo::afdo_annotate_cfg (promoted_stmts);
> compute_function_frequency ();
>
> /* Local pure-const may imply need to fixup the cfg. */
> - if (execute_fixup_cfg () & TODO_cleanup_cfg)
> + todo |= execute_fixup_cfg ();
> + if (todo & TODO_cleanup_cfg)
> cleanup_tree_cfg ();
>
> free_dominance_info (CDI_DOMINATORS);
> @@ -1674,7 +1677,7 @@ auto_profile (void)
> pop_cfun ();
> }
>
> - return TODO_rebuild_cgraph_edges;
> + return 0;
This change isn't mentioned - was it accidential?
Otherwise looks OK.
Thanks,
Richard.
> }
> } /* namespace autofdo. */
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2023-05-09 6:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 22:26 Eugene Rozenfeld
2023-05-09 6:40 ` Richard Biener [this message]
2023-05-09 22:05 ` [EXTERNAL] " Eugene Rozenfeld
2023-05-10 6:32 ` 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='CAFiYyc2=zNZ6yYFY96+c8ToAKBAm-_QBUFoSFPFfkbrCR24Vuw@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=Eugene.Rozenfeld@microsoft.com \
--cc=gcc-patches@gcc.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).