From: Jeff Law <jeffreyalaw@gmail.com>
To: Kito Cheng <kito.cheng@gmail.com>,
"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
Cc: "Kito.cheng" <kito.cheng@sifive.com>,
Robin Dapp <rdapp.gcc@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] RISC-V: Fix bug of tuple move splitter[PR112561]
Date: Fri, 17 Nov 2023 08:13:35 -0700 [thread overview]
Message-ID: <c07789e5-85dd-4fbc-9f20-35dc3821f3d4@gmail.com> (raw)
In-Reply-To: <CA+yXCZCCtDKAKudKKRt6yn896_63XCnRTsmLhcvY=CpU79JExQ@mail.gmail.com>
On 11/17/23 07:18, Kito Cheng wrote:
> I didn’t take a closer look yet on the ira/lra dump yet, but my feeling
> is that may cause by the earlyclober modifier isn’t work as expect?
>
> Let me take closer look tomorrow.
Remember that constraints aren't checked until register allocation. So
the combiner, splitters, etc don't know about "earlyclobber". It's a
relatively common goof.
Not sure if that's playing a role here, but I've seen it happen several
times in the past.
Jeff
next prev parent reply other threads:[~2023-11-17 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 7:35 Juzhe-Zhong
2023-11-17 8:49 ` Kito Cheng
2023-11-17 12:15 ` juzhe.zhong
2023-11-17 14:18 ` Kito Cheng
2023-11-17 15:13 ` Jeff Law [this message]
2023-11-18 9:59 ` Kito Cheng
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=c07789e5-85dd-4fbc-9f20-35dc3821f3d4@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=kito.cheng@sifive.com \
--cc=rdapp.gcc@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).