On 12/11/2023 11:26, Alejandro Colomar wrote: > The compiler will sometimes optimize them to normal *cpy(3) functions, > since the length of dst is usually known, if the previous *cpy(3) is > visible to the compiler. And they provide for cleaner code. If you > know that they'll get optimized, you could use them. May I ask, is there an example or document that shows this optimization by the compiler? Perhaps a godbolt link? So it's a strcat() optimized to a strcpy()? I know gcc might unroll and just include the values of the string bytes. Kind regards, Jonny
