From: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
To: "Robin Dapp" <rdapp.gcc@gmail.com>, kito.cheng <kito.cheng@gmail.com>
Cc: "Robin Dapp" <rdapp.gcc@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
palmer <palmer@dabbelt.com>,
jeffreyalaw <jeffreyalaw@gmail.com>
Subject: Re: Re: [PATCH] RISC-V: Add rawmemchr expander.
Date: Fri, 27 Oct 2023 15:52:17 +0800 [thread overview]
Message-ID: <7F5604B0140FB01D+202310271552166849400@rivai.ai> (raw)
In-Reply-To: <b5d953b4-b66c-4800-8958-fff6c69dd46e@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 631 bytes --]
I notice we have expand_block_move
in riscv-v.cc
Maybe we should move it into riscv-string.cc ?
juzhe.zhong@rivai.ai
From: Robin Dapp
Date: 2023-10-27 15:51
To: Kito Cheng; juzhe.zhong@rivai.ai
CC: rdapp.gcc; gcc-patches; palmer; jeffreyalaw
Subject: Re: [PATCH] RISC-V: Add rawmemchr expander.
> Could you put it into riscv-string.cc rather than riscv-v.cc? I would
> like to put those builtin function expander together if possible,
> riscv-string.cc might little bit confuse, but it's all included in
> string.h
Ok, sure. Will commit the adjusted patch if no further comments.
Regards
Robin
next prev parent reply other threads:[~2023-10-27 7:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 20:29 Robin Dapp
2023-10-26 22:37 ` 钟居哲
2023-10-27 7:38 ` Robin Dapp
2023-10-27 7:39 ` juzhe.zhong
2023-10-27 7:47 ` Kito Cheng
2023-10-27 7:51 ` Robin Dapp
2023-10-27 7:52 ` juzhe.zhong [this message]
2023-10-27 7:53 ` Robin Dapp
2023-10-27 8:50 ` Robin Dapp
2023-10-27 11:39 ` 钟居哲
2023-10-27 11:46 ` Robin Dapp
2023-10-27 13:38 ` Jeff Law
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=7F5604B0140FB01D+202310271552166849400@rivai.ai \
--to=juzhe.zhong@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.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).