public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jiufu Guo <guojiufu@linux.ibm.com>
To: Richard Biener <rguenther@suse.de>
Cc: Richard Biener <richard.guenther@gmail.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>,
	Segher Boessenkool <segher@kernel.crashing.org>,
	Bill Schmidt <wschmidt@linux.ibm.com>,
	David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH V2] Clean up loop-closed PHIs after loop finalize
Date: Mon, 16 Nov 2020 15:59:02 +0800	[thread overview]
Message-ID: <h48a6vh20mx.fsf@genoa.aus.stglabs.ibm.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.2011130906420.10073@p653.nepu.fhfr.qr> (Richard Biener's message of "Fri, 13 Nov 2020 09:18:46 +0100 (CET)")

Richard Biener <rguenther@suse.de> writes:

> On Wed, 11 Nov 2020, Jiufu Guo wrote:
>
>> 
>> Thanks a lot for the sugguestion from previous mails.
>> The patch was updated accordingly.
>> 
>> This updated patch propagates loop-closed PHIs them out after
>> loop_optimizer_finalize under a new introduced flag.  At some cases,
>> to clean up loop-closed PHIs would save efforts of optimization passes
>> after loopdone.
>> 
>> This patch passes bootstrap and regtest on ppc64le.  Is this ok for trunk?
>
> Comments below
>
>>    free_numbers_of_iterations_estimates (fn);
>>  
>> +  if (flag_clean_up_loop_closed_phi
>
> Sorry if there was miscommunication but I've not meant to add a
> new user-visible flag but instead a flag argument to loop_optimizer_finalize
> (as said, you can default it to false to only need to change the
> one in fini_loops)
Sorry for misunderstand.
Updated the patch.
>
>> +      && loops_state_satisfies_p (fn, LOOP_CLOSED_SSA))
>> +    {
>> +      clean_up_loop_closed_phi (fn);
>> +      loops_state_clear (fn, LOOP_CLOSED_SSA);
>> +    }
>> +
......
>> +  gphi *phi;
>> +  tree rhs;
>> +  tree lhs;
>> +  gphi_iterator gsi;
>> +  struct loop *loop;
>> +  bool cfg_altered = false;
>> +
>> +  /* Check dominator info before get loop-close PHIs from loop exits.  */
>> +  if (dom_info_state (CDI_DOMINATORS) != DOM_OK)
>
> Why?
>
As you said, loop_optimizer_finalize is also called from where dominator
info is not ready, e.g. called from: vrp(execute_vrp).
At there, loop exits info is not ready, and then
get_loop_exit_edges/get_loop_body_with_size function does not work.

>> +  /* Walk over loop in function.  */
>> +  FOR_EACH_LOOP_FN (fun, loop, 0)
>> +    {
>> +      /* Check each exit edege of loop.  */
>> +      auto_vec<edge> exits = get_loop_exit_edges (loop);
>> +      FOR_EACH_VEC_ELT (exits, i, e)
>> +	if (single_pred_p (e->dest))
>> +	  /* Walk over loop-closed PHIs.  */
>> +	  for (gsi = gsi_start_phis (e->dest); !gsi_end_p (gsi);)
>> +	    {
>> +	      phi = gsi.phi ();
>> +	      rhs = degenerate_phi_result (phi);
>
> You have a single predecessor, thus the result is always degenerate.
>
>> +	      lhs = gimple_phi_result (phi);
>> +
>> +	      if (rhs && may_propagate_copy (lhs, rhs))
>> +		{
>> +		  gimple_stmt_iterator psi = gsi;
>> +		  /* Advance the iterator before stmt is removed.  */
>> +		  gsi_next (&gsi);
>
> remove_phi_node should take care of this, you shouldn't need this
> (just do not advance the iterator when you remove the PHI node).
>
Yeap, get it! Thanks, will update the patch accordingly.
>> +
......
>> +
>> +		  replace_uses_by (lhs, rhs);
>> +		  remove_phi_node (&psi, true);
>> +		  cfg_altered = true;
>
> in the end the return value is unused but I think we should avoid
> altering the CFG since doing so requires it to be cleaned up for
> unreachable blocks.  That means to open-code replace_uses_by as
>
>   imm_use_iterator imm_iter;
>   use_operand_p use;
>   gimple *stmt;
>   FOR_EACH_IMM_USE_STMT (stmt, imm_iter, name)
>     {
>       FOR_EACH_IMM_USE_ON_STMT (use, imm_iter)
>         replace_exp (use, val);
>       update_stmt (stmt);
>     }

Thansk! This could also save some code in replace_uses_by.

BR. 
Jiufu Guo
>
> Thanks,
> Richard.
>
>> +		}
>> +	      else
>> +		gsi_next (&gsi);
>> +	    }
>> +    }
>> +
>> +  return cfg_altered;
>> +}
>> 

  reply	other threads:[~2020-11-16  7:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-05 13:18 [PATCH] Clean up loop-closed PHIs at loopdone pass guojiufu
2020-11-05 13:43 ` Richard Biener
2020-11-06  7:27   ` Jiufu Guo
2020-11-06  9:55     ` Richard Biener
2020-11-11  8:10       ` [PATCH V2] Clean up loop-closed PHIs after loop finalize Jiufu Guo
2020-11-13  8:18         ` Richard Biener
2020-11-16  7:59           ` Jiufu Guo [this message]
2020-11-16  9:26             ` Jiufu Guo
2020-11-16  9:35               ` Richard Biener
2020-11-17  5:58                 ` Jiufu Guo
2020-11-17  8:09                   ` Jiufu Guo
2020-11-17 10:21                     ` 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=h48a6vh20mx.fsf@genoa.aus.stglabs.ibm.com \
    --to=guojiufu@linux.ibm.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rguenther@suse.de \
    --cc=richard.guenther@gmail.com \
    --cc=segher@kernel.crashing.org \
    --cc=wschmidt@linux.ibm.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).