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: Wed, 14 Sep 2022 21:10:15 +0000 [thread overview]
Message-ID: <bug-106832-4-jmdHVpOq96@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 #8 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #5)
> BTW, for the case where -mabi=ieeelongdouble is the default unless there is
> some power* specific configuration in the library that needs to be done
> perhaps changing configure.tgt is all we need
Maybe a dumb question, but do we really need to support IBM 128 extended format
at all, regardless of whether long double is IBM128 or IEEE128? Meaning, since
D is "new" and we have no backwards compatibility issues, can we just say D
only supports IEEE128? ...assuming doing that can make things easier for us.
(In reply to Dan Horák from comment #3)
> - you need to start with GCC 11 as GCC 12 needs an existing gdc compiler
Yeah, I found that out pretty quickly :-)
> -
> https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=libphobos/configure.tgt;
> h=0063dd23249101b3506106ebbe32f454bcb829fb;hb=HEAD#l47 can go away, seems to
> build OK in GCC 11 without the line
Ah, but this is news to me. I'll kill my trunk build and remove that line and
re-kick things off. Thanks!
next prev parent reply other threads:[~2022-09-14 21:10 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 [this message]
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-jmdHVpOq96@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).