From: "nagachika (Tomoyuki Chikanaga) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "nagachika (Tomoyuki Chikanaga)" <ruby-core@ml.ruby-lang.org>
Subject: [ruby-core:113004] [Ruby master Bug#18997] Don't define ruby_qsort when POSIX qsort_r is available
Date: Sat, 25 Mar 2023 01:37:18 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-102537.20230325013718.52479@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-18997.20220908075035.52479@ruby-lang.org
Issue #18997 has been updated by nagachika (Tomoyuki Chikanaga).
Backport changed from 2.7: REQUIRED, 3.0: REQUIRED, 3.1: REQUIRED to 2.7: REQUIRED, 3.0: REQUIRED, 3.1: DONTNEED
I don't think this is necessary to backport to stable branches.
----------------------------------------
Bug #18997: Don't define ruby_qsort when POSIX qsort_r is available
https://bugs.ruby-lang.org/issues/18997#change-102537
* Author: delphij (Xin Li)
* Status: Closed
* Priority: Normal
* ruby -v: Not applicable
* Backport: 2.7: REQUIRED, 3.0: REQUIRED, 3.1: DONTNEED
----------------------------------------
The current code would define ruby_qsort as a wrapper of qsort_s when it is available. When both qsort_s and POSIX (GNU) qsort_r are available, we should call qsort_r directly instead, and the qsort_s wrapper is redundant.
Proposed patch at https://github.com/ruby/ruby/pull/6332 and can be applied on Ruby 2.7 and newer Ruby versions
--
https://bugs.ruby-lang.org/
______________________________________________
ruby-core mailing list -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/
prev parent reply other threads:[~2023-03-25 1:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 7:50 [ruby-core:109845] [Ruby master Bug#18997] Don't define ruby_qsort when POSIX qsort_r is available delphij (Xin Li)
2023-03-25 1:37 ` nagachika (Tomoyuki Chikanaga) via ruby-core [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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-102537.20230325013718.52479@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
--cc=ruby-core@ml.ruby-lang.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).