I am looking into slow memcpys and found that the multilib.yaml only points to _size variants of the libraries - specifically for all the "m" suffix targets. But the build includes both _size and non _size libraries. I found that I can point a custom multlib.yaml at the non _size versions but I'm wondering what your thoughts are on how to access these non _size libraries.
In my specific case, slow memcpy is in picolibc both _size and non _size and newlib _size. But newlib non _size includes the faster memcpy.
I am looking into slow memcpys and found that the multilib.yaml only points to _size variants of the libraries - specifically for all the "m" suffix targets. But the build includes both _size and non _size libraries. I found that I can point a custom multlib.yaml at the non _size versions but I'm wondering what your thoughts are on how to access these non _size libraries.
In my specific case, slow memcpy is in picolibc both _size and non _size and newlib _size. But newlib non _size includes the faster memcpy.