From: Lehua Ding <lehua.ding@rivai.ai>
To: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
"richard.sandiford" <richard.sandiford@arm.com>
Cc: jeffreyalaw <jeffreyalaw@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
"vmakarov@redhat.com" <vmakarov@redhat.com>
Subject: Re: [PATCH 0/7] ira/lra: Support subreg coalesce
Date: Mon, 13 Nov 2023 11:34:03 +0800 [thread overview]
Message-ID: <8EED9555B9D9A20C+3743277b-5069-49fb-bfa2-bb9c30e880dd@rivai.ai> (raw)
In-Reply-To: <F29484BD06D63234+202311130911457232486@rivai.ai>
On 2023/11/13 9:11, juzhe.zhong@rivai.ai wrote:
>>> Ah, nice! How configurable are the bit ranges?
> I think Lehua's patch is configurable for bit ranges.
> Since his patch allow target flexible tracking subreg livenesss
> according to REGMODE_NATURAL_SIZE
>
> +/* Return true if REGNO is a pseudo and MODE is a multil regs size. */
> +bool
> +need_track_subreg (int regno, machine_mode reg_mode)
> +{
> + poly_int64 total_size = GET_MODE_SIZE (reg_mode);
> + poly_int64 natural_size = REGMODE_NATURAL_SIZE (reg_mode);
> + return maybe_gt (total_size, natural_size)
> + && multiple_p (total_size, natural_size)
> + && regno >= FIRST_PSEUDO_REGISTER;
> +}
>
> It depends on how targets configure REGMODE_NATURAL_SIZE target hook.
>
> If we return QImode size, his patch is enable tracking bit ranges 7 bits
> subreg.
Yes, the current subreg_ranges class provides
remove_range/add_range/remove_ranges/add_ranges interfaces to modify
ranges. Each subreg_range contains start and end fields representing the
range [start, end). For live_subreg problem, the value returned by
REGMODE_NATURAL_SIZE is used as the unit, for bit track like Jeff's
side, it can be used bit as the unit.
--
Best,
Lehua (RiVAI)
lehua.ding@rivai.ai
next prev parent reply other threads:[~2023-11-13 3:34 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 3:47 Lehua Ding
2023-11-08 3:47 ` [PATCH 1/7] ira: Refactor the handling of register conflicts to make it more general Lehua Ding
2023-11-08 7:57 ` Richard Biener
2023-11-08 8:34 ` Lehua Ding
2023-11-08 3:47 ` [PATCH 2/7] ira: Add live_subreg problem and apply to ira pass Lehua Ding
2023-11-08 3:47 ` [PATCH 3/7] ira: Support subreg live range track Lehua Ding
2023-11-08 3:47 ` [PATCH 4/7] ira: Support subreg copy Lehua Ding
2023-11-08 3:47 ` [PATCH 5/7] ira: Add all nregs >= 2 pseudos to tracke subreg list Lehua Ding
2023-11-08 3:47 ` [PATCH 6/7] lra: Apply live_subreg df_problem to lra pass Lehua Ding
2023-11-08 3:47 ` [PATCH 7/7] lra: Support subreg live range track and conflict detect Lehua Ding
2023-11-08 3:55 ` [PATCH 0/7] ira/lra: Support subreg coalesce juzhe.zhong
2023-11-10 9:29 ` Lehua Ding
2023-11-08 9:40 ` Richard Sandiford
2023-11-08 19:13 ` Jeff Law
2023-11-10 9:43 ` Lehua Ding
2023-11-11 15:33 ` Richard Sandiford
2023-11-11 17:46 ` Jeff Law
2023-11-12 1:16 ` 钟居哲
2023-11-12 11:53 ` Richard Sandiford
2023-11-13 1:11 ` juzhe.zhong
2023-11-13 3:34 ` Lehua Ding [this message]
2023-11-10 9:26 ` Lehua Ding
2023-11-10 10:16 ` Richard Sandiford
2023-11-10 10:30 ` Lehua Ding
2023-11-10 10:39 ` Richard Sandiford
2023-11-10 14:28 ` Jeff Law
2023-11-08 16:56 ` Dimitar Dimitrov
2023-11-10 8:46 ` Lehua Ding
2023-11-10 8:53 ` Lehua Ding
2023-11-10 16:00 ` Dimitar Dimitrov
2023-11-12 6:06 ` Lehua Ding
2023-11-12 10:08 ` Lehua Ding
2023-11-09 20:24 ` Vladimir Makarov
2023-11-10 7:59 ` Richard Biener
2023-11-12 12:01 ` Lehua Ding
2023-11-12 12:12 ` Lehua Ding
2023-11-13 19:25 ` Vladimir Makarov
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=8EED9555B9D9A20C+3743277b-5069-49fb-bfa2-bb9c30e880dd@rivai.ai \
--to=lehua.ding@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=richard.sandiford@arm.com \
--cc=vmakarov@redhat.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).