https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116010
--- Comment #6 from Thiago Jung Bauermann <thiago.bauermann at linaro dot org> --- (In reply to Andrew Pinski from comment #5) > (In reply to Thiago Jung Bauermann from comment #3) > > > First gcc.target/arm/simd/mve-vabs.c now calls memcpy because of the > > > restrict instead of memmove. That should be a simple fix there. > > > > In my setup I don't see memcpy being called. Instead of memmove, GCC is now > > generating the load and store instruction. E.g.: > > Well that is an inlined version of memcpy. I was looking at what was done in > the tree dump to see the difference. Ah, thanks for clarifying! So apparently the path forward is to remove the memmove check from mve-vabs.c. Or is there a way to test inlined memcpy?
