public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Adhemerval Zanella <azanella@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc/azanella/clang] math: Do not use __builtin_isinf on clang Date: Fri, 29 Apr 2022 14:10:00 +0000 (GMT) [thread overview] Message-ID: <20220429141000.B88D63856DCF@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=ee783241cc4cb722230855de0943ee0a4bb7cf4f commit ee783241cc4cb722230855de0943ee0a4bb7cf4f Author: Adhemerval Zanella <adhemerval.zanella@linaro.org> Date: Fri Apr 1 17:03:34 2022 -0300 math: Do not use __builtin_isinf on clang It does not handle pseudo normal numbers. Diff: --- math/math.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/math/math.h b/math/math.h index 8e64e2eb4f..1cac405f67 100644 --- a/math/math.h +++ b/math/math.h @@ -1012,7 +1012,8 @@ enum /* Return nonzero value if X is positive or negative infinity. */ # if __HAVE_DISTINCT_FLOAT128 && !__GNUC_PREREQ (7,0) \ - && !defined __SUPPORT_SNAN__ && !defined __cplusplus + && !defined __SUPPORT_SNAN__ && !defined __cplusplus \ + && !defined __clang__ /* Since __builtin_isinf_sign is broken for float128 before GCC 7.0, use the helper function, __isinff128, with older compilers. This is only provided for C mode, because in C++ mode, GCC has no support @@ -1021,8 +1022,7 @@ enum # define isinf(x) \ (__builtin_types_compatible_p (__typeof (x), _Float128) \ ? __isinff128 (x) : __builtin_isinf_sign (x)) -# elif (__GNUC_PREREQ (4,4) && !defined __SUPPORT_SNAN__) \ - || __glibc_clang_prereq (3,7) +# elif (__GNUC_PREREQ (4,4) && !defined __SUPPORT_SNAN__) # define isinf(x) __builtin_isinf_sign (x) # else # define isinf(x) __MATH_TG ((x), __isinf, (x))
next reply other threads:[~2022-04-29 14:10 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-29 14:10 Adhemerval Zanella [this message] -- strict thread matches above, loose matches on Subject: below -- 2024-04-17 20:12 Adhemerval Zanella 2024-04-02 15:59 Adhemerval Zanella 2024-02-09 17:37 Adhemerval Zanella 2024-02-07 14:12 Adhemerval Zanella 2024-01-29 18:02 Adhemerval Zanella 2023-12-21 18:59 Adhemerval Zanella 2023-09-28 17:57 Adhemerval Zanella 2023-08-30 12:41 Adhemerval Zanella 2023-02-09 19:53 Adhemerval Zanella 2022-10-28 17:47 Adhemerval Zanella 2022-10-04 13:04 Adhemerval Zanella 2022-06-09 21:26 Adhemerval Zanella 2022-06-09 13:22 Adhemerval Zanella 2022-06-03 14:11 Adhemerval Zanella 2022-05-13 14:25 Adhemerval Zanella 2022-05-12 19:39 Adhemerval Zanella 2022-05-10 18:30 Adhemerval Zanella 2022-04-04 13:00 Adhemerval Zanella
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=20220429141000.B88D63856DCF@sourceware.org \ --to=azanella@sourceware.org \ --cc=glibc-cvs@sourceware.org \ /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: linkBe 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).