Ah, please also ensure to include (and follow) the stringop_strategy
checks. (LIBCALL, VECTOR)
The naming is a bit unfortunate still but that need not be fixed
in this patch.
Regards
Robin
Hi Sergei,
thanks for contributing this!
Small general remarks/nits upfront:
The code looks like it hasn't been run through clang-format or
similar. Please make sure that it adheres to the GNU coding
conventions. The same applies to comments. Some of them start
in lowercase.
As you rely on t
gcc/ChangeLog
* config/riscv/riscv.md (movmem): Use riscv_vector::expand_block_move,
if and only if we know the entire operation can be performed using one
vector
load followed by one vector store
gcc/testsuite/ChangeLog
* gcc.target/riscv/rvv/base/movmem-1.c: New test
---
gcc/