From: Andreas Schwab <schwab@suse.de>
To: Jakub Jelinek via Gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Richard Biener <rguenther@suse.de>,
Jakub Jelinek <jakub@redhat.com>, FX <fxcoudert@gmail.com>,
"Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: [PATCH] Implement __builtin_issignaling
Date: Mon, 15 Aug 2022 14:04:19 +0200 [thread overview]
Message-ID: <mvmfshxiugs.fsf@suse.de> (raw)
In-Reply-To: <YvoyWKejnpp3sFEZ@tucnak> (Jakub Jelinek via Gcc-patches's message of "Mon, 15 Aug 2022 13:47:36 +0200")
On Aug 15 2022, Jakub Jelinek via Gcc-patches wrote:
> That seems like a glibc bug/weird feature in the __MATH_TG macro
> or _Generic.
__MATH_TG is only defined for real floating types, since all of the type
generic macros in <math.h> only accept real floating types.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2022-08-15 12:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 10:12 Jakub Jelinek
2022-08-15 11:24 ` Richard Biener
2022-08-15 11:47 ` Jakub Jelinek
2022-08-15 12:04 ` Andreas Schwab [this message]
2022-08-15 12:07 ` Richard Biener
2022-08-15 13:06 ` Jakub Jelinek
2022-08-16 11:33 ` Jakub Jelinek
2022-08-16 11:41 ` Richard Biener
2022-08-16 11:57 ` Jakub Jelinek
2022-08-16 12:04 ` Richard Biener
2022-08-23 7:58 ` Patch ping (Re: [PATCH] Implement __builtin_issignaling) Jakub Jelinek
2022-08-23 18:23 ` Joseph Myers
2022-08-23 19:21 ` [PATCH] v2: Implement __builtin_issignaling Jakub Jelinek
2022-08-15 16:14 ` [PATCH] " FX
2022-08-15 16:23 ` Jakub Jelinek
2022-08-15 20:52 ` Uros Bizjak
2022-08-25 19:23 ` Michael Meissner
2022-08-25 19:56 ` Jakub Jelinek
2022-08-26 17:25 ` Michael Meissner
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=mvmfshxiugs.fsf@suse.de \
--to=schwab@suse.de \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=rguenther@suse.de \
/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).