From: "H.J. Lu" <hjl.tools@gmail.com>
To: Noah Goldstein <goldstein.w.n@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Update string/test-memmove.c to cover 16KB copy
Date: Fri, 20 Aug 2021 07:08:08 -0700 [thread overview]
Message-ID: <CAMe9rOqonuXpMoMvsyPM1rRNvxpzoDWdYXsUosSPgfrcuT2k6g@mail.gmail.com> (raw)
In-Reply-To: <CAFUsyfKp6=HbiJ0-SXqwuwNnqmqJ5+zL3CdoGUVtELtd+i7gaQ@mail.gmail.com>
On Thu, Aug 19, 2021 at 8:10 PM Noah Goldstein <goldstein.w.n@gmail.com> wrote:
>
>
>
> On Thu, Aug 19, 2021, 2:10 PM H.J. Lu via Libc-alpha <libc-alpha@sourceware.org> wrote:
>>
>> ---
>> string/test-memmove.c | 49 +++++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 49 insertions(+)
>>
>> diff --git a/string/test-memmove.c b/string/test-memmove.c
>> index b271248b1d..812f6bde9e 100644
>> --- a/string/test-memmove.c
>> +++ b/string/test-memmove.c
>> @@ -312,6 +312,52 @@ do_test2 (size_t offset)
>> munmap ((void *) large_buf, size);
>> }
>>
>> +static void
>> +do_test3 (void)
>
>
> I think it may be cleaner to make
> bytes_move and offset function arguments.
Fixed.
>> +{
>> + /* Copy 16KB data. */
>> + size_t bytes_move = 16384;
>
>
> I think this should be a function argument.
Fixed.
>> + size_t size = 16384 * 3;
>> + uint32_t *buf;
>> +
>> + buf = mmap (NULL, size, PROT_READ | PROT_WRITE,
>> + MAP_PRIVATE | MAP_ANON, -1, 0);
>> +
>> + if (buf == MAP_FAILED)
>> + error (EXIT_UNSUPPORTED, errno, "mmap failed");
>> +
>> + size_t arr_size = bytes_move / sizeof (uint32_t);
>> + size_t i;
>> +
>> + FOR_EACH_IMPL (impl, 0)
>> + {
>> + for (i = 0; i < arr_size; i++)
>> + buf[i] = (uint32_t) i;
>> +
>> + uint32_t *dst = &buf[arr_size + 3];
>
>
> I think + 3 should be a variable and passed to the function.
Fixed.
>> +
>> +#ifdef TEST_BCOPY
>> + CALL (impl, (char *) buf, (char *) dst, bytes_move);
>> +#else
>> + CALL (impl, (char *) dst, (char *) buf, bytes_move);
>> +#endif
>> +
>> + for (i = 0; i < arr_size; i++)
>> + {
>> + if (dst[i] != (uint32_t) i)
>> + {
>> + error (0, 0,
>> + "Wrong result in function %s dst \"%p\" src \"%p\" offset \"%zd\"",
>> + impl->name, dst, buf, i);
>> + ret = 1;
>> + break;
>> + }
>> + }
>> + }
>> +
>> + munmap ((void *) buf, size);
>> +}
>> +
>> int
>> test_main (void)
>> {
>> @@ -356,6 +402,9 @@ test_main (void)
>> do_test2 (0x200000);
>> do_test2 (0x4000000 - 1);
>> do_test2 (0x4000000);
>> +
>> + do_test3 ();
>>
>> +
>> return ret;
>> }
>>
>> --
>> 2.31.1
>
>
> Okay with this patch but see comments.
I sent out the v2 patch.
Thanks.
--
H.J.
prev parent reply other threads:[~2021-08-20 14:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 19:10 H.J. Lu
2021-08-20 3:09 ` Noah Goldstein
2021-08-20 14:08 ` H.J. Lu [this message]
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=CAMe9rOqonuXpMoMvsyPM1rRNvxpzoDWdYXsUosSPgfrcuT2k6g@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=goldstein.w.n@gmail.com \
--cc=libc-alpha@sourceware.org \
/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).