This is the mail archive of the
mailing list for the glibc project.
Re: while working on an optimized version of strnlen, some string tests fail
- From: Nam-goo Lee <devnglee at gmail dot com>
- To: libc-help at sourceware dot org
- Cc: joseph at codesourcery dot com
- Date: Tue, 6 Dec 2016 00:21:36 +0900
- Subject: Re: while working on an optimized version of strnlen, some string tests fail
- Authentication-results: sourceware.org; auth=none
- References: <CAEjPfw0FMybM-GNrwz5kqgXHRqQTNwG8079wMp6Qvybg5ZDRZA@mail.gmail.com> <email@example.com> <CAEjPfw3bdNTBiWXkq7jE4+wNx9CXuZpAP66+_Zzc_LTpwKwwsg@mail.gmail.com> <firstname.lastname@example.org>
>> malloc/tst-malloc-thread-fail.out says "Timed out: killed the child process".
>> Is it possible that this test failure relates to something with my
>> test environment, rather than my implementation?
>> I'm testing on an ODROID-XU4 board.
It turns out that the test "malloc/tst-malloc-thread-fail" FAILs even
without my implementation.
Can this get upstream review?
With the provided benchmark test from the source tree,
this optimized strnlen is 1.3~4 times faster for inputs longer than 16,
and is similar in speed for inputs shorter than that.