public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "juzhe.zhong at rivai dot ai" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106694] Redundant move instructions in ARM SVE intrinsics use cases
Date: Tue, 07 Nov 2023 22:08:42 +0000 [thread overview]
Message-ID: <bug-106694-4-V9DjVqftLW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106694-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106694
--- Comment #11 from JuzheZhong <juzhe.zhong at rivai dot ai> ---
(In reply to Richard Sandiford from comment #10)
> Some of the SME changes I'm working on fix this, but I'm not sure how widely
> we'll be able to use them on non-SME code. Assigning myself just in case.
Hi, Richard. We are going to fix subreg issue by subreg liveness tracking on
IRA/LRA.
Hopefully today.
next prev parent reply other threads:[~2023-11-07 22:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-106694-4@http.gcc.gnu.org/bugzilla/>
2022-10-27 23:00 ` pinskia at gcc dot gnu.org
2022-10-27 23:12 ` pinskia at gcc dot gnu.org
2022-10-27 23:15 ` pinskia at gcc dot gnu.org
2023-11-07 22:06 ` rsandifo at gcc dot gnu.org
2023-11-07 22:08 ` juzhe.zhong at rivai dot ai [this message]
2023-11-08 3:58 ` juzhe.zhong at rivai dot ai
2023-12-07 19:41 ` cvs-commit at gcc dot gnu.org
2023-12-07 19:52 ` rsandifo at gcc dot gnu.org
2024-02-27 8:37 ` pinskia at gcc dot gnu.org
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=bug-106694-4-V9DjVqftLW@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).