From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: cpp /usr/include/threads.h fails; modfl segfaults
Date: Sun, 30 Aug 2020 14:07:51 -0600 [thread overview]
Message-ID: <d59590dc-552c-db45-0049-b5a287f36773@SystematicSw.ab.ca> (raw)
In-Reply-To: <871rjod54j.fsf@Otto.invalid>
On 2020-08-30 00:23, ASSI wrote:
> Ken Brown via Cygwin writes:
>> OK, so the problem was introduced between 3.1.4 and 3.1.5. It should
>> be pretty easy to bisect and find the culprit. I'll do that tomorrow
>> if no one beats me to it.
>
> The most likely culprit would be this I think:
>
> https://sourceware.org/git/?p=newlib-cygwin.git;a=commitdiff;h=4ad9ba42fc3dd116bad8b9cb89d434256d3431fb
>
> If so and depending on why exactly it fails, there might be more fallout
> from other similar changes.
OP debugged to display winsup/cygwin/math/modfl.c assembler that hasn't
changed since added, so compiler, build, or runtime environment updates may have
changed the code generated or used e.g. predefined symbols, build flags, runtime
CPU features.
Does Cygwin detect and allow GCC builtins to be used where available, keeping
the function available for fallback where the compiler can't use the builtin?
--
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-30 20:07 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
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 [this message]
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=d59590dc-552c-db45-0049-b5a287f36773@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).