<div dir="auto">That was, if I recall correctly, about the C standard library interfaces in the Null-terminated multibyte strings section. Basically that the character at a time interfaces are not amenable to vectorization. <div dir="auto"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Sep 1, 2019, 11:55 Henri Sivonen <<a href="mailto:hsivonen@hsivonen.fi">hsivonen@hsivonen.fi</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Sat, Aug 31, 2019 at 10:16 PM Tom Honermann <<a href="mailto:tom@honermann.net" target="_blank" rel="noreferrer">tom@honermann.net</a>> wrote:<br>
><br>
> The summary for the SG16 meeting held August 21st, 2019 is now available. For those that attended, please review and suggest corrections:<br>
> - <a href="https://github.com/sg16-unicode/sg16-meetings#august-21st-2019" rel="noreferrer noreferrer" target="_blank">https://github.com/sg16-unicode/sg16-meetings#august-21st-2019</a><br>
<br>
The minutes say:<br>
<br>
> C interfaces can't achieve the performance that Bob Steagall demonstrated with his UTF-8 work.<br>
<br>
What's that about? Does it mean that interfaces that assume<br>
zero-terminated sentinel-based strings can't achieve the performance?<br>
Surely a C interface that identifies both the source and the<br>
destination by pointer and length can.<br>
<br>
-- <br>
Henri Sivonen<br>
<a href="mailto:hsivonen@hsivonen.fi" target="_blank" rel="noreferrer">hsivonen@hsivonen.fi</a><br>
<a href="https://hsivonen.fi/" rel="noreferrer noreferrer" target="_blank">https://hsivonen.fi/</a><br>
_______________________________________________<br>
SG16 Unicode mailing list<br>
<a href="mailto:Unicode@isocpp.open-std.org" target="_blank" rel="noreferrer">Unicode@isocpp.open-std.org</a><br>
<a href="http://www.open-std.org/mailman/listinfo/unicode" rel="noreferrer noreferrer" target="_blank">http://www.open-std.org/mailman/listinfo/unicode</a><br>
</blockquote></div>