From: Jeff Law <jeffreyalaw@gmail.com>
To: Uros Bizjak <ubizjak@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Introduce VIRTUAL_REGISTER_P and VIRTUAL_REGISTER_NUM_P predicates
Date: Tue, 18 Apr 2023 11:17:13 -0600 [thread overview]
Message-ID: <7fc633ef-db4f-df30-3496-21900afaef3a@gmail.com> (raw)
In-Reply-To: <CAFULd4ana5uk0Xkmn=6rok+-uMpCsGwC8=i2mxHXGd+vNr0V5g@mail.gmail.com>
On 4/17/23 15:27, Uros Bizjak via Gcc-patches wrote:
> These two predicates are similar to existing HARD_REGISTER_P and
> HARD_REGISTER_NUM_P predicates and return 1 if the given register
> corresponds to a virtual register.
>
> gcc/ChangeLog:
>
> * rtl.h (VIRTUAL_REGISTER_P): New predicate.
> (VIRTUAL_REGISTER_NUM_P): Ditto.
> (REGNO_PTR_FRAME_P): Use VIRTUAL_REGISTER_NUM_P predicate.
> * expr.cc (force_operand): Use VIRTUAL_REGISTER_P predicate.
> * function.cc (instantiate_decl_rtl): Ditto.
> * rtlanal.cc (rtx_addr_can_trap_p_1): Ditto.
> (nonzero_address_p): Ditto.
> (refers_to_regno_p): Use VIRTUAL_REGISTER_NUM_P predicate.
>
> Bootstrapped and regression tested on x86_64-linux-gnu {,-m32}.
>
> OK for master?
OK.
Jeff
next prev parent reply other threads:[~2023-04-18 17:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 21:27 Uros Bizjak
2023-04-18 17:17 ` Jeff Law [this message]
2023-04-18 17:20 ` Jakub Jelinek
2023-04-19 6:53 ` Uros Bizjak
2023-04-19 7:28 ` Jakub Jelinek
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=7fc633ef-db4f-df30-3496-21900afaef3a@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ubizjak@gmail.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).