https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112109
--- Comment #7 from Jeffrey A. Law ---
We could close and open an new issue to honor TARGET_MAX_LMUL, or just reuse
this one after an adjustment of the title. No strong preference.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112109
--- Comment #6 from Robin Dapp ---
Should we close this? I think all of the routines are in or are we missing
something still?
What's IMHO still a TODO is to honor TARGET_MAX_LMUL for some of the builtins
that came first. memcpy for example a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112109
--- Comment #5 from GCC Commits ---
The master branch has been updated by Jeff Law :
https://gcc.gnu.org/g:42946aa9b3228262e413481a3193bda85c20ef4b
commit r15-1723-g42946aa9b3228262e413481a3193bda85c20ef4b
Author: Sergei Lewis
Date: Sat Jun
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112109
--- Comment #4 from GCC Commits ---
The master branch has been updated by Jeff Law :
https://gcc.gnu.org/g:df15eb15b5f820321c81efc75f0af13ff8c0dd5b
commit r15-439-gdf15eb15b5f820321c81efc75f0af13ff8c0dd5b
Author: Sergei Lewis
Date: Mon May
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112109
--- Comment #3 from GCC Commits ---
The master branch has been updated by Robin Dapp :
https://gcc.gnu.org/g:d468718c9a097aeb8794fb1a2df6db2c1064d7f7
commit r14-6341-gd468718c9a097aeb8794fb1a2df6db2c1064d7f7
Author: Robin Dapp
Date: Fri Dec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112109
--- Comment #2 from GCC Commits ---
The master branch has been updated by Robin Dapp :
https://gcc.gnu.org/g:2664964b2f695e947faea4c29dbddd3615cc4b0b
commit r14-6340-g2664964b2f695e947faea4c29dbddd3615cc4b0b
Author: Robin Dapp
Date: Fri Dec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112109
--- Comment #1 from Kito Cheng ---
Just note:
I would like to introduce `-mstringop-strategy=`, `-mmemcpy-strategy=` and
-mmemset-strategy=` option to control the behavior like x86.
the possible option list from my mind is:
- auto: current st
