public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Richard Biener <rguenth@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-107] Remove duplicate DFS walks from DF init Date: Thu, 20 Apr 2023 09:23:49 +0000 (GMT) [thread overview] Message-ID: <20230420092349.9AEE93854176@sourceware.org> (raw) https://gcc.gnu.org/g:974326fd5199a8ae8482f2a521b1edd449a2fa9e commit r14-107-g974326fd5199a8ae8482f2a521b1edd449a2fa9e Author: Richard Biener <rguenther@suse.de> Date: Mon Feb 20 15:02:43 2023 +0100 Remove duplicate DFS walks from DF init The following removes unused CFG order computes from rest_of_handle_df_initialize. The CFG orders are computed from df_analyze (). This also removes code duplication that would have to be kept in sync. * df-core.cc (rest_of_handle_df_initialize): Remove computation of df->postorder, df->postorder_inverted and df->n_blocks. Diff: --- gcc/df-core.cc | 5 ----- 1 file changed, 5 deletions(-) diff --git a/gcc/df-core.cc b/gcc/df-core.cc index 3286ffda2ce..de5cbd0c622 100644 --- a/gcc/df-core.cc +++ b/gcc/df-core.cc @@ -701,11 +701,6 @@ rest_of_handle_df_initialize (void) if (optimize > 1) df_live_add_problem (); - df->postorder = XNEWVEC (int, last_basic_block_for_fn (cfun)); - df->n_blocks = post_order_compute (df->postorder, true, true); - inverted_post_order_compute (&df->postorder_inverted); - gcc_assert ((unsigned) df->n_blocks == df->postorder_inverted.length ()); - df->hard_regs_live_count = XCNEWVEC (unsigned int, FIRST_PSEUDO_REGISTER); df_hard_reg_init ();
reply other threads:[~2023-04-20 9:23 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230420092349.9AEE93854176@sourceware.org \ --to=rguenth@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).