From: "Maciej W. Rozycki" <macro@embecosm.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: gcc-patches@gcc.gnu.org, Ulrich Weigand <uweigand@de.ibm.com>,
Richard Sandiford <richard.sandiford@arm.com>
Subject: Re: [PATCH] PR middle-end/103059: reload: Also accept ASHIFT with indexed addressing
Date: Fri, 5 Nov 2021 00:18:41 +0000 (GMT) [thread overview]
Message-ID: <alpine.DEB.2.20.2111042357320.8821@tpp.orcam.me.uk> (raw)
In-Reply-To: <3d74d8f5-2182-abc9-6c06-cf8a9b8f94de@gmail.com>
On Thu, 4 Nov 2021, Jeff Law wrote:
> Sometimes the language we're using in email is not as crisp as it should be. So
> just to be clear, the canonicalization I'm referring to is only in effect within
> a MEM. It does not apply to address calculations that happen outside a MEM. I
> think that is consistent with Richard's comments.
Ah, OK then.
> > and then reload substitutes (reg/v:SI 154 [ n_ctrs ]) with the inner MEM
> > as it fails to reload the pseudo and just uses its memory location.
> OK. So what I still don't see is why we would need to re-recognize. You're
> changing code that I thought was only applicable when we were reloading an
> address inside a MEM and if we're inside a MEM, then we shouldn't be seeing an
> ASHIFT. We're replacing the argument of the ASHIFT.
Well, the context of this code (around and including hunk #1) is:
else if (insn_extra_address_constraint
(lookup_constraint (constraints[i])))
{
address_operand_reloaded[i]
= find_reloads_address (recog_data.operand_mode[i], (rtx*) 0,
recog_data.operand[i],
recog_data.operand_loc[i],
i, operand_type[i], ind_levels, insn);
/* If we now have a simple operand where we used to have a
PLUS or MULT, re-recognize and try again. */
if ((OBJECT_P (*recog_data.operand_loc[i])
|| GET_CODE (*recog_data.operand_loc[i]) == SUBREG)
&& (GET_CODE (recog_data.operand[i]) == MULT
|| GET_CODE (recog_data.operand[i]) == PLUS))
{
INSN_CODE (insn) = -1;
retval = find_reloads (insn, replace, ind_levels, live_known,
reload_reg_p);
return retval;
}
so the body of the conditional is specifically executed for an address and
not a MEM; in this particular case matched with the plain "p" constraint.
MEMs are handled with the next conditional right below.
> So, overall, I'm still confused as to why the patch has any effect at all.
Does the explanation above clear your confusion?
Maciej
next prev parent reply other threads:[~2021-11-05 0:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 13:53 Maciej W. Rozycki
2021-11-04 18:12 ` Jeff Law
2021-11-04 21:04 ` Maciej W. Rozycki
2021-11-04 23:47 ` Jeff Law
2021-11-05 0:18 ` Maciej W. Rozycki [this message]
2021-11-09 0:26 ` Jeff Law
2021-11-10 16:41 ` Maciej W. Rozycki
2021-11-23 19:04 ` Jeff Law
2021-11-24 13:20 ` Maciej W. Rozycki
2021-11-24 13:25 ` Richard Biener
2021-11-24 13:38 ` Maciej W. Rozycki
2021-11-06 2:38 ` Hans-Peter Nilsson
2021-11-07 21:22 ` Maciej W. Rozycki
2021-11-08 4:15 ` Hans-Peter Nilsson
2021-11-08 10:00 ` Maciej W. Rozycki
2021-11-12 23:22 ` Hans-Peter Nilsson
2021-11-07 21:24 ` Maciej W. Rozycki
2021-11-09 11:59 ` Maciej W. Rozycki
2021-11-08 19:55 ` Hans-Peter Nilsson
2021-11-09 12:11 ` Maciej W. Rozycki
2021-11-08 19:55 ` Hans-Peter Nilsson
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=alpine.DEB.2.20.2111042357320.8821@tpp.orcam.me.uk \
--to=macro@embecosm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=richard.sandiford@arm.com \
--cc=uweigand@de.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).