This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Implement strlcat [BZ#178]
- From: Paul Eggert <eggert at cs dot ucla dot edu>
- To: Florian Weimer <fweimer at redhat dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Thu, 10 Dec 2015 15:13:27 -0800
- Subject: Re: [PATCH] Implement strlcat [BZ#178]
- Authentication-results: sourceware.org; auth=none
- References: <56547472 dot 3010302 at redhat dot com> <5654B1FE dot 5020100 at cs dot ucla dot edu> <5654B796 dot 7070302 at redhat dot com> <5656E018 dot 5020608 at cs dot ucla dot edu> <565F211A dot 2030909 at redhat dot com> <56607CD1 dot 3050209 at cs dot ucla dot edu> <566197FD dot 9020001 at redhat dot com> <5661F59C dot 5050608 at cs dot ucla dot edu> <5669D382 dot 1080803 at redhat dot com>
On 12/10/2015 11:33 AM, Florian Weimer wrote:
I see that you have added a reference to -fcheck-pointer-bounds. Do you
have practical experience with this option?
No, I'm afraid we are not up-to-date with the latest Intel hardware
here; my usual development platform at UCLA runs a 5.5-year-old AMD CPU,
alas. I will try to get my hands on a Skylake, but this may take some
time. In the meantime my impression is that -fcheck-pointer-bounds works
well enough for some packages when using recent-enough hardware and
software, and I expect that by the time the next glibc comes out
-fcheck-pointer-bounds will be more-used and better-supported. I suppose
we could add wording to the glibc manual to say that
-fcheck-pointer-bounds is bleeding-edge as of 2015.
It is amusing that -fcheck-pointer-bounds removes the main justification
for strlcpy+strlcat. What timing!