public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tuliom at ascii dot art.br" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug math/30550] New: powerpc64le: GCC-specific code for isinf() is being used on clang Date: Tue, 13 Jun 2023 21:46:54 +0000 [thread overview] Message-ID: <bug-30550-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30550 Bug ID: 30550 Summary: powerpc64le: GCC-specific code for isinf() is being used on clang Product: glibc Version: 2.39 Status: NEW Severity: normal Priority: P2 Component: math Assignee: unassigned at sourceware dot org Reporter: tuliom at ascii dot art.br Target Milestone: --- The error can be reproduced with the following: $ cat test-isinf.c #include <math.h> _Bool classify(long double x) { return isinf(x); } $ clang -c -mabi=ibmlongdouble -mfloat128 test-isinf.c test-isinf.c:3:46: error: passing 'long double' to parameter of incompatible type '_Float128' (aka '__float128') _Bool classify(long double x) { return isinf(x); } ^ /usr/include/math.h:1026:21: note: expanded from macro 'isinf' ? __isinff128 (x) : __builtin_isinf_sign (x)) ^ /usr/include/bits/mathcalls-helper-functions.h:29:45: note: passing argument to parameter '__value' here __MATHDECL_ALIAS (int, __isinf,, (_Mdouble_ __value), isinf) ^ 1 error generated. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-06-13 21:46 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-13 21:46 tuliom at ascii dot art.br [this message] 2023-06-13 21:47 ` [Bug math/30550] " tuliom at ascii dot art.br 2023-06-13 21:58 ` tuliom at ascii dot art.br 2023-06-30 22:13 ` cvs-commit at gcc dot gnu.org 2023-06-30 22:18 ` tuliom at ascii dot art.br
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=bug-30550-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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).