public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug d/112957] New: [13/14 regression] src/std/math/exponential.d doesn't compile on 32-bit FreeBSD/x86 Date: Mon, 11 Dec 2023 10:13:46 +0000 [thread overview] Message-ID: <bug-112957-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112957 Bug ID: 112957 Summary: [13/14 regression] src/std/math/exponential.d doesn't compile on 32-bit FreeBSD/x86 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: d Assignee: ibuclaw at gdcproject dot org Reporter: ro at gcc dot gnu.org CC: andreast at gcc dot gnu.org Target Milestone: --- Host: x86_64-unknown-freebsd14.0 Target: x86_64-unknown-freebsd14.0 Build: x86_64-unknown-freebsd14.0 Building both GCC 13.2.0 and trunk on FreeBSD 14.0 failed in the same way: /vol/gcc/src/gcc-13.2.0/libphobos/src/std/math/exponential.d:1977:9: error: stat ic assert: "no coefficients for exp2()" 1977 | static assert(0, "no coefficients for exp2()"); | ^ /vol/gcc/src/gcc-13.2.0/libphobos/src/std/math/exponential.d:1684:20: note: inst antiated from here: ‘exp2Impl!real’ 1684 | return exp2Impl(x); | ^ gmake[9]: *** [Makefile:1285: std/json.lo] Error 1 Only the 32-bit multilib is affected. I suspect this is due to the unusual format of long double on 32-bit FreeBSD/x86: i386/freebsd.h has #define TARGET_96_ROUND_53_LONG_DOUBLE (!TARGET_64BIT)
next reply other threads:[~2023-12-11 10:13 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-11 10:13 ro at gcc dot gnu.org [this message] 2023-12-11 10:14 ` [Bug d/112957] " ro at gcc dot gnu.org 2024-05-07 7:43 ` [Bug d/112957] [13/14/15 " rguenth at gcc dot gnu.org
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-112957-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).