From: Xi Ruoyao <xry111@xry111.site>
To: gcc-patches@gcc.gnu.org
Cc: chenglulu <chenglulu@loongson.cn>,
i@xen0n.name, xuchenghua@loongson.cn, c@jia.je,
Xi Ruoyao <xry111@xry111.site>
Subject: [PATCH 0/2] LoongArch: Fix PR113033 and clean up code
Date: Tue, 19 Dec 2023 14:59:55 +0800 [thread overview]
Message-ID: <20231219065957.70665-1-xry111@xry111.site> (raw)
Superseds
https://gcc.gnu.org/pipermail/gcc-patches/2023-December/640871.html.
Per Jakub's response, vec_init patterns do not have a predicate on the
input operand so the operand can be *anything*. It's not safe to simply
move it into an reg, and we have to use force_reg instead.
The code clean up is separated into the 2nd patch to make reviewing
easier.
Bootstrapped and regtested on loongarch64-linux-gnu. Ok for trunk?
Xi Ruoyao (2):
LoongArch: Use force_reg instead of gen_reg_rtx + emit_move_insn in
vec_init expander [PR113033]
LoongArch: Clean up vec_init expander
gcc/config/loongarch/loongarch.cc | 54 +++++++------------
gcc/testsuite/gcc.target/loongarch/pr113033.c | 23 ++++++++
2 files changed, 43 insertions(+), 34 deletions(-)
create mode 100644 gcc/testsuite/gcc.target/loongarch/pr113033.c
--
2.43.0
next reply other threads:[~2023-12-19 7:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 6:59 Xi Ruoyao [this message]
2023-12-19 6:59 ` [PATCH 1/2] LoongArch: Use force_reg instead of gen_reg_rtx + emit_move_insn in vec_init expander [PR113033] Xi Ruoyao
2023-12-19 6:59 ` [PATCH 2/2] LoongArch: Clean up vec_init expander Xi Ruoyao
2023-12-19 7:26 ` [PATCH 0/2] LoongArch: Fix PR113033 and clean up code chenglulu
2023-12-20 3:52 ` Chenghui Pan
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=20231219065957.70665-1-xry111@xry111.site \
--to=xry111@xry111.site \
--cc=c@jia.je \
--cc=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=i@xen0n.name \
--cc=xuchenghua@loongson.cn \
/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).