From: "Zack Weinberg" <zack@owlfolio.org>
To: "Kuan-Wei Chiu" <visitorckw@gmail.com>,
"Florian Weimer" <fweimer@redhat.com>
Cc: "GNU libc development" <libc-alpha@sourceware.org>,
"Adhemerval Zanella" <adhemerval.zanella@linaro.org>,
goldstein.w.n@gmail.com
Subject: Re: [PATCH] stdlib: Optimize number of calls to comparison function
Date: Tue, 05 Dec 2023 15:35:33 -0500 [thread overview]
Message-ID: <f1c21245-3386-4e5d-b05c-967e8d0bfd1e@app.fastmail.com> (raw)
In-Reply-To: <ZW4a52600gzaB5vx@visitorckw-System-Product-Name>
On Mon, Dec 4, 2023, at 1:31 PM, Kuan-Wei Chiu wrote:
> On Mon, Dec 04, 2023 at 09:20:50AM +0100, Florian Weimer wrote:
>> I think the factor in stdlib/tst-qsort5.c needs to be adjusted:
>>
>> /* This is an arbitrary factor which is true for the current
>> implementation across a wide range of sizes. */
>> TEST_VERIFY (factor <= 4.5);
>
> It seems that the factor can be adjusted to around 3.5. I can send
> another patch for this adjustment or resend it as a patch series.
Before you go any further with this patch series I think we need to
decide whether our backward compatibility constraints mean our qsort
has to be a stable sort. If so, we should make it *always* be a
stable sort and write that into the documentation, and that would
mean junking the entire heapsort implementation.
I do not have a strong opinion either way, but I do think it should
either *always* or *never* be stable, i.e. not the previous state of
"whether you get a stable sort depends on the size of the input and
various other undocumented factors." Also, I think that the
behavior should not depend on which version of glibc a program
was compiled against.
zw
next prev parent reply other threads:[~2023-12-05 20:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 21:48 [PATCH] stdlib: Optimize number of calls to comparison function Kuan-Wei Chiu
2023-12-04 8:20 ` Florian Weimer
2023-12-04 18:31 ` Kuan-Wei Chiu
2023-12-05 10:44 ` Florian Weimer
2023-12-05 20:00 ` Kuan-Wei Chiu
2023-12-05 20:35 ` Zack Weinberg [this message]
2023-12-06 10:21 ` Florian Weimer
2023-12-06 12:51 ` Adhemerval Zanella Netto
2023-12-17 15:42 ` Zack Weinberg
2023-12-17 15:55 ` Florian Weimer
2023-12-17 16:47 ` Kuan-Wei Chiu
2023-12-17 18:02 ` Florian Weimer
2023-12-05 3:22 ` [PATCH v2 0/2] stdlib: Optimize number of calls to comparison function in qsort Kuan-Wei Chiu
2023-12-05 3:22 ` [PATCH v2 1/2] " Kuan-Wei Chiu
2023-12-05 3:22 ` [PATCH v2 2/2] stdlib: Adjust the factor in tst-qsort5 Kuan-Wei Chiu
2024-02-16 7:08 ` [PATCH] stdlib: Optimize number of calls to comparison function Kuan-Wei Chiu
2024-03-27 19:45 ` Adhemerval Zanella Netto
2024-03-27 19:59 ` Kuan-Wei Chiu
2024-03-27 20:42 ` Adhemerval Zanella Netto
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f1c21245-3386-4e5d-b05c-967e8d0bfd1e@app.fastmail.com \
--to=zack@owlfolio.org \
--cc=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--cc=goldstein.w.n@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=visitorckw@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).