From: Eliot Moss <moss@cs.umass.edu>
To: Ken Brown <kbrown@cornell.edu>,
airplanemath <airplanemath@aol.com>,
cygwin@cygwin.com
Subject: Re: [QUAR] Re: cpp /usr/include/threads.h fails; modfl segfaults
Date: Sun, 30 Aug 2020 14:21:58 -0400 [thread overview]
Message-ID: <e541c805-1521-cf98-3f1b-77715da9fc62@cs.umass.edu> (raw)
In-Reply-To: <0fa6ed3d-c665-68a7-3d3e-9f570a236058@cornell.edu>
On 8/30/2020 12:11 PM, Ken Brown wrote:
> On 8/29/2020 5:41 PM, Eliot Moss wrote:
>> It seems the math functions in winsup were not built quite right ...
>
> That's a pretty broad generalization to make based on one reported bug (which Corinna fixed within
> 24 hours of the report).
I certainly did not mean to offend or demean anyone or their work.
I think what I said is true, in some sense - that particular function
was broken in certain versions. I sing Corinna's praises all the time,
and greatly value all the volunteer work here! (Sometimes manage to
help a little myself.) What I was pointing to was that the issue was
not in the OP's program or gcc's compilation or optimization thereof,
but that the issue was in the (compiled version of the) mod function
itself ...
This helps indicate who might be able to diagnose and fix it ...
Regards - EM
next prev parent reply other threads:[~2020-08-30 18:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <02b16d2e-9d51-de58-807b-3b31b2565b59.ref@aol.com>
2020-08-29 12:52 ` airplanemath
2020-08-29 17:57 ` Ken Brown
2020-08-29 21:41 ` [QUAR] " Eliot Moss
2020-08-30 16:11 ` Ken Brown
2020-08-30 18:21 ` Eliot Moss [this message]
2020-08-30 1:21 ` airplanemath
2020-08-30 2:56 ` Ken Brown
2020-08-30 6:23 ` ASSI
2020-08-30 20:07 ` Brian Inglis
2020-08-30 13:00 ` Corinna Vinschen
2020-08-30 19:21 ` airplanemath
2020-08-31 7:33 ` Corinna Vinschen
2020-08-30 20:39 ` Brian Inglis
2020-08-31 7:35 ` Corinna Vinschen
2020-08-31 15:37 ` Brian Inglis
2020-08-31 18:45 ` Corinna Vinschen
2020-08-31 19:24 ` Brian Inglis
2020-08-31 19:41 ` Corinna Vinschen
2020-09-01 17:28 ` Brian Inglis
2020-09-02 7:54 ` 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=e541c805-1521-cf98-3f1b-77715da9fc62@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=airplanemath@aol.com \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
/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).