From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: Noah Goldstein <goldstein.w.n@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] tests/string: Drop simple/stupid/builtin tests
Date: Wed, 6 Apr 2022 11:38:11 +0530 [thread overview]
Message-ID: <2aded52c-c84a-92d4-0fe8-96a9894101ac@sourceware.org> (raw)
In-Reply-To: <CAFUsyfJYeB1bCpwtPPZV_jTFssA6+-pBpW_qnoSfXg=KgqfU-w@mail.gmail.com>
On 06/04/2022 01:58, Noah Goldstein wrote:
> On Tue, Apr 5, 2022 at 12:05 AM Siddhesh Poyarekar via Libc-alpha
> <libc-alpha@sourceware.org> wrote:
>>
>> In most cases the simple/stupid/builtin functions were in there to
>> benchmark optimized implementations against. Only in some cases the
>> functions are used to check expected results.
>>
>> Remove these tests from IMPL() and only keep them in wherever they're
>> used for a specific purpose, e.g. to generate expected results.
>>
>> This improves timing of `make subdirs=string` by over a minute and a
>> half (over 15%) on a Whiskey Lake laptop.
>
> Makes sense, although I would prefer if we kept the simple* functions
> and just removed them from the test list.
>
> When adding new tests it's nice to have a guaranteed reference
> to test the test...
>
> What do you think?
I don't feel too strongly either way, I'll send v2 with in-test variants
retained where none exists so that they may be used in future if need
arises.
Thanks,
Siddhesh
next prev parent reply other threads:[~2022-04-06 6:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 5:05 Siddhesh Poyarekar
2022-04-05 20:28 ` Noah Goldstein
2022-04-06 6:08 ` Siddhesh Poyarekar [this message]
2022-04-06 6:52 ` [PATCH v2] " Siddhesh Poyarekar
2022-04-06 14:20 ` Noah Goldstein
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=2aded52c-c84a-92d4-0fe8-96a9894101ac@sourceware.org \
--to=siddhesh@sourceware.org \
--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).