From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: cygwin qsort erratic
Date: Sun, 30 Aug 2020 20:54:58 -0600 [thread overview]
Message-ID: <c9792fdc-aedc-6934-e11f-732f841b533b@SystematicSw.ab.ca> (raw)
In-Reply-To: <CAHybJinLYpcviSFiJ=V-EZqoatEzjFfr9DOUzxzmofUmtwMS+w@mail.gmail.com>
On 2020-08-30 15:27, Kurt-Karen Carlson-Lougheed via Cygwin wrote:
> In a small percentage of qsort requests, the results are erratic. Running
> the same code under Linux (RHEL7) does NOT have this problem. I updated my
> cygwin to current and the problem persists. I copied the latest netbsd.org
> qsort.c and compiled into my code, the problem is resolved with that
> version of qsort.
>
> In researching this issue, there was a post to this list 2015-01-11
> reporting a
> 'damaged' qsort. This may still be the same issue. The netbsd version I am
> now using is dated 2017-05-19.
>
> My code experiencing this is SourceForge uac19, I'll be posting the
> corrected version (v3.2) with the netbsd qsort tomorrow after completing
> validation tests. I would ultimately like to see cygwin's qsort fixed.
As qsort depends on the array object data types and comparison functions, please
post a Simple Test Case, showing at least those types and function(s), and the
faulty output results.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-08-31 2:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 21:27 Kurt-Karen Carlson-Lougheed
2020-08-31 2:54 ` Brian Inglis [this message]
2020-08-31 17:50 ` Kurt-Karen Carlson-Lougheed
2020-08-31 18:00 ` Thomas Wolff
2020-08-31 18:50 ` Brian Inglis
2020-09-01 20:29 ` Kurt-Karen Carlson-Lougheed
2020-09-01 20:55 ` Stephen John Smoogen
2020-09-01 22:00 ` Thomas Wolff
2020-09-02 0:26 ` Kurt-Karen Carlson-Lougheed
2020-09-02 7:23 ` Thomas Wolff
2020-08-31 7:31 ` Corinna Vinschen
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=c9792fdc-aedc-6934-e11f-732f841b533b@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.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).