From: Noah Goldstein <goldstein.w.n@gmail.com>
To: Sunil K Pandey <skpgkp2@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Improve test coverage of strnlen function
Date: Wed, 2 Jun 2021 13:26:30 -0400 [thread overview]
Message-ID: <CAFUsyf+By4kCiBAyc4W3PRJbDXMDpr9FK2pYWrLcsOvZOnEY8A@mail.gmail.com> (raw)
In-Reply-To: <20210602161029.799090-1-skpgkp2@gmail.com>
On Wed, Jun 2, 2021 at 12:13 PM Sunil K Pandey via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
> This patch covers the following condition:
>
> Strings start with different alignments and end with less than 512 byte
> length.
> ---
> string/test-strnlen.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/string/test-strnlen.c b/string/test-strnlen.c
> index d70faa26ab..20e645893a 100644
> --- a/string/test-strnlen.c
> +++ b/string/test-strnlen.c
> @@ -271,6 +271,10 @@ test_main (void)
> do_test (1, 1 << i, 5000, BIG_CHAR);
> }
>
> + for (i = 1; i <= 127; i++)
I think it makes sense to either include 0 or 128 for alignments
as in some implementations (x86 avx2/evex for example)
that is a unique case.
> + for (size_t length = i; length < 512; length++)
> + do_test (i, length, 512, BIG_CHAR);
Might be strengthened a bit with additional test case
in inner loop:
do_test (getpagesize() - i, length, 512, BIG_CHAR);
> +
> do_random_tests ();
> do_page_tests ();
> do_page_2_tests ();
> --
> 2.31.1
>
next prev parent reply other threads:[~2021-06-02 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 16:10 Sunil K Pandey
2021-06-02 17:26 ` Noah Goldstein [this message]
2021-06-02 17:33 ` Noah Goldstein
2021-06-02 20:57 ` Sunil Pandey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFUsyf+By4kCiBAyc4W3PRJbDXMDpr9FK2pYWrLcsOvZOnEY8A@mail.gmail.com \
--to=goldstein.w.n@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=skpgkp2@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).