> I had a quick glance at the glibc source code and didn't find anything other than a C implementation - do you know if that's a recent innovation or what versi

> I had a quick glance at the glibc source code and didn't find anything other than a C implementation - do you know if that's a recent innovation or what version of glibc supports that? Or is any V implementation in glibc's string functions just relying on the compiler autovectorization (does that exist for RVV)? Or is this not upstream yet? Last I heard the glibc developers are waiting for a decent hardware platform to target. You need something that supports V1.0, is widely available, and performs something like we expect future hardware to perform so you don't end up optimizing for the wrong things. (Qemu is no use because the performance of emulated V is very different from the real thing since every V instruction goes through a TCG helper function.)