From: Jeff Law <jeffreyalaw@gmail.com>
To: Richard Sandiford <richard.sandiford@arm.com>,
jlaw@ventanamicro.com, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 1/6] rtl-ssa: Ensure global registers are live on exit
Date: Tue, 24 Oct 2023 11:21:30 -0600 [thread overview]
Message-ID: <a3d5a297-a479-4ff7-8872-6c7d6d397c3b@gmail.com> (raw)
In-Reply-To: <20231024105006.3337671-2-richard.sandiford@arm.com>
On 10/24/23 04:50, Richard Sandiford wrote:
> RTL-SSA mostly relies on DF for block-level register liveness
> information, including artificial uses and defs at the beginning
> and end of blocks. But one case was missing. DF does not add
> artificial uses of global registers to the beginning or end
> of a block. Instead it marks them as used within every block
> when computing LR and LIVE problems.
>
> For RTL-SSA, global registers behave like memory, which in
> turn behaves like gimple vops. We need to ensure that they
> are live on exit so that final definitions do not appear
> to be unused.
>
> Also, the previous live-on-exit handling only considered the exit
> block itself. It needs to consider non-local gotos as well, since
> they jump directly to some code in a parent function and so do
> not have a path to the exit block.
>
> gcc/
> * rtl-ssa/blocks.cc (function_info::add_artificial_accesses): Force
> global registers to be live on exit. Handle any block with zero
> successors like an exit block.
OK
jeff
next prev parent reply other threads:[~2023-10-24 17:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 10:50 [PATCH 0/6] rtl-ssa: Various fixes needed for the late-combine pass Richard Sandiford
2023-10-24 10:50 ` [PATCH 1/6] rtl-ssa: Ensure global registers are live on exit Richard Sandiford
2023-10-24 17:21 ` Jeff Law [this message]
2023-10-24 10:50 ` [PATCH 2/6] rtl-ssa: Create REG_UNUSED notes after all pending changes Richard Sandiford
2023-10-24 17:22 ` Jeff Law
2023-10-24 10:50 ` [PATCH 3/6] rtl-ssa: Fix ICE when deleting memory clobbers Richard Sandiford
2023-10-24 17:24 ` Jeff Law
2023-10-24 10:50 ` [PATCH 4/6] rtl-ssa: Handle artifical uses of deleted defs Richard Sandiford
2023-10-24 17:26 ` Jeff Law
2023-10-24 10:50 ` [PATCH 5/6] rtl-ssa: Calculate dominance frontiers for the exit block Richard Sandiford
2023-10-24 17:28 ` Jeff Law
2023-10-24 10:50 ` [PATCH 6/6] rtl-ssa: Handle call clobbers in more places Richard Sandiford
2023-10-24 17: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=a3d5a297-a479-4ff7-8872-6c7d6d397c3b@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jlaw@ventanamicro.com \
--cc=richard.sandiford@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).