public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug d/106832] Missing powerpc64le-linux support for D Date: Sat, 17 Sep 2022 00:12:32 +0000 [thread overview] Message-ID: <bug-106832-4-Y1TxdleTpB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106832-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106832 --- Comment #21 from Peter Bergner <bergner at gcc dot gnu.org> --- (In reply to Peter Bergner from comment #20) > So going back to my IBM128 build, I see that libphobos does have some code > relating to mant_dig == 106 which is IBM128/IBM double-double, including in > the file that's ICEing here due to the assert. I've patched two asserts to > allow IBM128 and I'm re-kicking off a bootstrap and regtest. It might be > that the only problem the asserts needed updating? We'll see. For the record, this is what I'm testing with: diff --git a/libphobos/configure.tgt b/libphobos/configure.tgt index 0063dd23249..e78688010ed 100644 --- a/libphobos/configure.tgt +++ b/libphobos/configure.tgt @@ -44,7 +44,6 @@ case "${target}" in ;; power*-*-linux*) LIBPHOBOS_SUPPORTED=yes - LIBDRUNTIME_ONLY=yes ;; riscv*-*-linux*) LIBPHOBOS_SUPPORTED=yes diff --git a/libphobos/src/std/math/package.d b/libphobos/src/std/math/package.d index 19982ec216a..d0752032d1f 100644 --- a/libphobos/src/std/math/package.d +++ b/libphobos/src/std/math/package.d @@ -318,13 +318,14 @@ do version (LittleEndian) { static assert(real.mant_dig == 53 || real.mant_dig == 64 - || real.mant_dig == 113, + || real.mant_dig == 106 || real.mant_dig == 113, "Only 64-bit, 80-bit, and 128-bit reals"~ " are supported for LittleEndian CPUs"); } else { - static assert(real.mant_dig == 53 || real.mant_dig == 113, + static assert(real.mant_dig == 53 || real.mant_dig == 106 + || real.mant_dig == 113, "Only 64-bit and 128-bit reals are supported for BigEndian CPUs."); }
next prev parent reply other threads:[~2022-09-17 0:12 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-05 7:33 [Bug d/106832] New: " jakub at gcc dot gnu.org 2022-09-14 20:21 ` [Bug d/106832] " bergner at gcc dot gnu.org 2022-09-14 20:32 ` jakub at gcc dot gnu.org 2022-09-14 20:32 ` dan at danny dot cz 2022-09-14 20:38 ` jakub at gcc dot gnu.org 2022-09-14 20:43 ` jakub at gcc dot gnu.org 2022-09-14 20:44 ` dan at danny dot cz 2022-09-14 20:46 ` jakub at gcc dot gnu.org 2022-09-14 21:10 ` bergner at gcc dot gnu.org 2022-09-14 21:13 ` bergner at gcc dot gnu.org 2022-09-14 21:28 ` ibuclaw at gdcproject dot org 2022-09-14 21:30 ` jakub at gcc dot gnu.org 2022-09-14 21:43 ` ibuclaw at gdcproject dot org 2022-09-14 21:56 ` bergner at gcc dot gnu.org 2022-09-14 23:44 ` bergner at gcc dot gnu.org 2022-09-15 4:20 ` ibuclaw at gcc dot gnu.org 2022-09-15 6:49 ` dan at danny dot cz 2022-09-15 13:54 ` bergner at gcc dot gnu.org 2022-09-15 13:56 ` kalevlember at gmail dot com 2022-09-16 18:35 ` bergner at gcc dot gnu.org 2022-09-17 0:03 ` bergner at gcc dot gnu.org 2022-09-17 0:12 ` bergner at gcc dot gnu.org [this message] 2022-09-17 2:16 ` bergner at gcc dot gnu.org 2022-09-17 2:23 ` bergner at gcc dot gnu.org 2022-09-17 4:37 ` ibuclaw at gdcproject dot org 2022-09-17 4:46 ` ibuclaw at gdcproject dot 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-106832-4-Y1TxdleTpB@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).