From: "Li Xu" <xuli1@eswincomputing.com>
To: juzhe.zhong <juzhe.zhong@rivai.ai>,
"Jeff Law" <jeffreyalaw@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Cc: kito.cheng <kito.cheng@gmail.com>, palmer <palmer@dabbelt.com>,
"Robin Dapp" <rdapp.gcc@gmail.com>
Subject: Re: Re: [PATCH] RISC-V: Implement -mmemcpy-strategy= options[PR112537]
Date: Mon, 20 Nov 2023 10:51:57 +0800 [thread overview]
Message-ID: <202311201051573679142@eswincomputing.com> (raw)
In-Reply-To: <993F704C2E671F9E+202311200955454099191@rivai.ai>
[-- Attachment #1: Type: text/plain, Size: 2325 bytes --]
Committed, thanks jeff and juzhe.
Thanks,
Li Xu
xuli1@eswincomputing.com
From: juzhe.zhong@rivai.ai
Date: 2023-11-20 09:55
To: Li Xu; jeffreyalaw; gcc-patches
CC: kito.cheng; palmer; Robin Dapp
Subject: Re: Re: [PATCH] RISC-V: Implement -mmemcpy-strategy= options[PR112537]
Jeff has approved your patch.
You can commit it now.
Btw, CC Robin to let him know this patch.
Since he will support strcpy/strlen....etc builtin with RVV instruction sequence.
He will definitely needs compile option like this patch introduce.
Thanks.
juzhe.zhong@rivai.ai
From: Li Xu
Date: 2023-11-20 09:09
To: Jeff Law; gcc-patches
CC: kito.cheng; palmer; juzhe.zhong
Subject: Re: Re: [PATCH] RISC-V: Implement -mmemcpy-strategy= options[PR112537]
I've tested it and there are no issues with regression testing.
Thanks,
Li Xu
xuli1@eswincomputing.com
From: Jeff Law
Date: 2023-11-20 05:42
To: Li Xu; gcc-patches
CC: kito.cheng; palmer; juzhe.zhong
Subject: Re: [PATCH] RISC-V: Implement -mmemcpy-strategy= options[PR112537]
On 11/16/23 22:12, Li Xu wrote:
> From: xuli<xuli1@eswincomputing.com>
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112537
>
> -mmemcpy-strategy=[auto|libcall|scalar|vector]
>
> auto: Current status, use scalar or vector instructions.
> libcall: Always use a library call.
> scalar: Only use scalar instructions.
> vector: Only use vector instructions.
>
> PR target/112537
>
> gcc/ChangeLog:
>
> * config/riscv/riscv-opts.h (enum riscv_stringop_strategy_enum): Strategy enum.
> * config/riscv/riscv-string.cc (riscv_expand_block_move): Disabled based on options.
> (expand_block_move): Ditto.
> * config/riscv/riscv.opt: Add -mmemcpy-strategy=.
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/riscv/rvv/base/cpymem-strategy-1.c: New test.
> * gcc.target/riscv/rvv/base/cpymem-strategy-2.c: New test.
> * gcc.target/riscv/rvv/base/cpymem-strategy-3.c: New test.
> * gcc.target/riscv/rvv/base/cpymem-strategy-4.c: New test.
> * gcc.target/riscv/rvv/base/cpymem-strategy-5.c: New test.
> * gcc.target/riscv/rvv/base/cpymem-strategy.h: New test.
This is OK assuming you have tested it to ensure there aren't any
regressions in the testsuite. I don't expect problems, but let's be
sure :-)
Thanks,
jeff
prev parent reply other threads:[~2023-11-20 2:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 5:12 Li Xu
2023-11-19 21:42 ` Jeff Law
2023-11-20 1:09 ` Li Xu
2023-11-20 1:55 ` juzhe.zhong
2023-11-20 2:51 ` Li Xu [this message]
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=202311201051573679142@eswincomputing.com \
--to=xuli1@eswincomputing.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--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).