public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kewen.Lin" <linkw@linux.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Vladimir Makarov <vmakarov@redhat.com>,
	Bill Schmidt <wschmidt@linux.ibm.com>
Subject: Re: [PATCH] ira: Skip some pseudos in move_unallocated_pseudos
Date: Wed, 23 Dec 2020 14:40:53 +0800	[thread overview]
Message-ID: <07bd112b-a767-5ba6-720e-3e8873c72d42@linux.ibm.com> (raw)
In-Reply-To: <20201222135546.GD2672@gate.crashing.org>

Hi Segher,

on 2020/12/22 下午9:55, Segher Boessenkool wrote:
> Hi!
> 
> Just a dumb formatting comment:
> 
> On Tue, Dec 22, 2020 at 04:05:39PM +0800, Kewen.Lin wrote:
>> This patch is to make move_unallocated_pseudos consistent
>> to what we have in function find_moveable_pseudos, where we
>> record the original pseudo into pseudo_replaced_reg only if
>> validate_change succeeds with newreg.  To ensure every
>> unallocated pseudo in move_unallocated_pseudos has expected
>> information, it's better to add a check and skip it if it's
>> unexpected.  This avoids possible ICEs in future.
>>
>> btw, I happened to found this in the bootstrapping for one
>> experimental local patch, which is considered as impractical.
> 
>> --- a/gcc/ira.c
>> +++ b/gcc/ira.c
>> @@ -5111,6 +5111,11 @@ move_unallocated_pseudos (void)
>>        {
>>  	int idx = i - first_moveable_pseudo;
>>  	rtx other_reg = pseudo_replaced_reg[idx];
>> +	/* If there is no appropriate pseudo in pseudo_replaced_reg, it
>> +	   means validate_change fails for this new pseudo in function
>> +	   find_moveable_pseudos, then bypass it here.*/
> 
> Dot space space.

Good catch, thanks!  I forgot to reformat after polishing the comments.
Will fix it with other potential comments.

> 
> The patch sounds fine to me.  Hard to tell without seeing the patch that
> exposed the problem (for onlookers like me who do not know this code
> well, anyway ;-) )

The patch which made this issue exposed looks like:

+; Like *rotl<mode>3_insert_3 but work with nonzero_bits rather than
+; explicit AND.
+(define_insn "*rotl<mode>3_insert_8"
+  [(set (match_operand:GPR 0 "gpc_reg_operand" "=r")
+        (ior:GPR (ashift:GPR (match_operand:GPR 1 "gpc_reg_operand" "r")
+                             (match_operand:SI 2 "u6bit_cint_operand" "n"))
+                 (match_operand:GPR 3 "gpc_reg_operand" "0")))]
+  "HOST_WIDE_INT_1U << INTVAL (operands[2])
+   > nonzero_bits (operands[3], <MODE>mode)"
+{
+  if (<MODE>mode == SImode)
+    return "rlwimi %0,%1,%h2,0,31-%h2";
+  else
+    return "rldimi %0,%1,%H2,0";
+}
+  [(set_attr "type" "insert")])

Some insn matches this pattern in combine, later ira tries to introduce
one new pseudo since it meets the checks in find_moveable_pseudos, but
it fails in the call to validate_change since the nonzero_bits is more
rough and can't satisfy the pattern condition, leaving the unexpected
entry in pseudo_replaced_reg.

BR,
Kewen

  reply	other threads:[~2020-12-23  6:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-22  8:05 Kewen.Lin
2020-12-22 13:55 ` Segher Boessenkool
2020-12-23  6:40   ` Kewen.Lin [this message]
2021-01-04 23:13     ` Jeff Law
2021-01-05  2:36       ` Kewen.Lin
2021-01-05 18:19         ` Jeff Law
2021-01-06  3:12           ` Kewen.Lin
2021-01-08 20:37             ` Jeff Law

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=07bd112b-a767-5ba6-720e-3e8873c72d42@linux.ibm.com \
    --to=linkw@linux.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=segher@kernel.crashing.org \
    --cc=vmakarov@redhat.com \
    --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).