From: Richard Sandiford <richard.sandiford@arm.com>
To: Alex Coplan <alex.coplan@arm.com>
Cc: gcc-patches@gcc.gnu.org, Kyrylo Tkachov <kyrylo.tkachov@arm.com>,
Richard Earnshaw <richard.earnshaw@arm.com>
Subject: Re: [PATCH 1/4] rtl-ssa: Run finalize_new_accesses forwards [PR113070]
Date: Mon, 22 Jan 2024 13:27:17 +0000 [thread overview]
Message-ID: <mptfrypqz0q.fsf@arm.com> (raw)
In-Reply-To: <ZaKvlmv7yjTpcUTB@arm.com> (Alex Coplan's message of "Sat, 13 Jan 2024 15:43:18 +0000")
Alex Coplan <alex.coplan@arm.com> writes:
> The next patch in this series exposes an interface for creating new uses
> in RTL-SSA. The intent is that new user-created uses can consume new
> user-created defs in the same change group. This is so that we can
> correctly update uses of memory when inserting a new store pair insn in
> the aarch64 load/store pair fusion pass (the affected uses need to
> consume the new store pair insn).
>
> As it stands, finalize_new_accesses is called as part of the backwards
> insn placement loop within change_insns, but if we want new uses to be
> able to depend on new defs in the same change group, we need
> finalize_new_accesses to be called on earlier insns first. This is so
> that when we process temporary uses and turn them into permanent uses,
> we can follow the last_def link on the temporary def to ensure we end up
> with a permanent use consuming a permanent def.
>
> Bootstrapped/regtested on aarch64-linux-gnu, OK for trunk?
>
> Thanks,
> Alex
>
> gcc/ChangeLog:
>
> PR target/113070
> * rtl-ssa/changes.cc (function_info::change_insns): Split out the call
> to finalize_new_accesses from the backwards placement loop, run it
> forwards in a separate loop.
OK, thanks.
Richard
> ---
> gcc/rtl-ssa/changes.cc | 21 ++++++++++++++++-----
> 1 file changed, 16 insertions(+), 5 deletions(-)
>
> diff --git a/gcc/rtl-ssa/changes.cc b/gcc/rtl-ssa/changes.cc
> index 2fac45ae885..e538b637848 100644
> --- a/gcc/rtl-ssa/changes.cc
> +++ b/gcc/rtl-ssa/changes.cc
> @@ -775,15 +775,26 @@ function_info::change_insns (array_slice<insn_change *> changes)
> placeholder = add_placeholder_after (after);
> following_insn = placeholder;
> }
> -
> - // Finalize the new list of accesses for the change. Don't install
> - // them yet, so that we still have access to the old lists below.
> - finalize_new_accesses (change,
> - placeholder ? placeholder : insn);
> }
> placeholders[i] = placeholder;
> }
>
> + // Finalize the new list of accesses for each change. Don't install them yet,
> + // so that we still have access to the old lists below.
> + //
> + // Note that we do this forwards instead of in the backwards loop above so
> + // that any new defs being inserted are processed before new uses of those
> + // defs, so that the (initially) temporary uses referring to temporary defs
> + // can be easily updated to become permanent uses referring to permanent defs.
> + for (unsigned i = 0; i < changes.size (); i++)
> + {
> + insn_change &change = *changes[i];
> + insn_info *placeholder = placeholders[i];
> + if (!change.is_deletion ())
> + finalize_new_accesses (change,
> + placeholder ? placeholder : change.insn ());
> + }
> +
> // Remove all definitions that are no longer needed. After the above,
> // the only uses of such definitions should be dead phis and now-redundant
> // live-out uses.
prev parent reply other threads:[~2024-01-22 13:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-13 15:43 Alex Coplan
2024-01-17 14:42 ` Jeff Law
2024-01-17 14:49 ` Alex Coplan
2024-01-22 13:27 ` Richard Sandiford [this message]
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=mptfrypqz0q.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=alex.coplan@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@arm.com \
--cc=richard.earnshaw@arm.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).