From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: FX <fxcoudert@gmail.com>
Cc: fortran@gcc.gnu.org
Subject: Re: New signaling NaN causes 12 testsuite failures
Date: Tue, 25 Jan 2022 12:45:44 -0800 [thread overview]
Message-ID: <20220125204544.GE69322@troutmask.apl.washington.edu> (raw)
In-Reply-To: <154020AE-C99E-400F-B86C-A8AF4720F16F@gmail.com>
On Tue, Jan 25, 2022 at 08:52:34PM +0100, FX wrote:
> > With --disable-multilib, so no -m32 support, I still
> > signaling_3.f90 failing. In
> >
> > ! { dg-do run { xfail { { i?86-*-* x86_64-*-* } && ilp32 } } }
> > ! x87 / x86-32 ABI is unsuitable for signaling NaNs
>
> This just means the test shouldn’t be run on 32-bit Intel.
>
> Can you run this:
>
> #include <stdint.h>
> #include <stdio.h>
> #include "issignaling_fallback.h"
>
> int main (void) {
> long double z;
>
> z = __builtin_nansl("");
> printf("%d\n", issignaling(z));
>
> z = __builtin_nanl("");
> printf("%d\n", issignaling(z));
> }
>
> compiled with -fsignaling-nans and the issignaling_fallback.h file from libgfortran?
>
If in issignaling_fallback.h, I change
#if __FLOAT_WORD_ORDER == __BIG_ENDIAN
...
#elif __FLOAT_WORD_ORDER == __LITTLE_ENDIAN
...
#endif
to
#if 0
...
#else
...
#endif
to force little endian, I get
% ~/work/x/bin/gcc -o -I. -fsignaling-nans -o z b.c && ./z
1
0
so need an equivalent of __FLOAT_WORD_ORDER for at least
FreeBSD.
Found it. https://gcc.gnu.org/onlinedocs/cpp/Common-Predefined-Macros.html
Add trailing undersores to __FLOAT_WORD_ORDER and change
__BIG_ENDIAN to __ORDER_BIG_ENDIAN__. Likewise for LITTLE.
--
Steve
next prev parent reply other threads:[~2022-01-25 20:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 0:44 Steve Kargl
2022-01-25 2:48 ` Steve Kargl
2022-01-25 8:05 ` FX
2022-01-25 17:42 ` Steve Kargl
2022-01-25 19:59 ` Steve Kargl
2022-01-25 20:04 ` FX
2022-01-25 20:20 ` Steve Kargl
2022-01-25 8:09 ` FX
2022-01-25 16:52 ` Steve Kargl
2022-01-25 19:35 ` Steve Kargl
2022-01-25 19:52 ` FX
2022-01-25 20:12 ` Steve Kargl
2022-01-25 20:45 ` Steve Kargl [this message]
2022-01-25 20:56 ` FX
2022-01-25 21:05 ` Steve Kargl
2022-01-25 23:11 ` FX
2022-01-26 10:47 ` Tobias Burnus
2022-01-26 16:02 ` Steve Kargl
2022-01-26 16:19 ` FX
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=20220125204544.GE69322@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@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).