public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub 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: Wed, 14 Sep 2022 20:32:21 +0000 [thread overview]
Message-ID: <bug-106832-4-CASM2yORHi@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 #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Well, I certainly see libphobos/configure.tgt having powerpc*-linux* as the
only target that does:
power*-*-linux*)
LIBPHOBOS_SUPPORTED=yes
LIBDRUNTIME_ONLY=yes
;;
I believe the latter means it builds only a small part of libphobos and I think
the reason is the long double stuff (I think D has float/double/real types and
the last one is the largest floating point available). Now, because IBM
extended and IEEE quad are effectively unordered (neither is subset nor
superset of the other), it is hard to determine which one is actually larger,
but IEEE quad has both higher exponent range and larger mantissa precision for
most of number, it is just those cases closely around values representable in
double that can have higher precision in IBM extended.
next prev parent reply other threads:[~2022-09-14 20:32 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 [this message]
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
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-CASM2yORHi@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: 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).