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: Fri, 16 Sep 2022 18:35:33 +0000 [thread overview]
Message-ID: <bug-106832-4-mkV8Aj5oJy@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 #19 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Peter Bergner from comment #17)
> Bah, you are correct. I forgot I needed to add an explicit configure option
> to get the IEEE128 default. I'll kick it off again! Thanks!
Ok, my Fedora36 (ie, a default IEEE128 system) bootstrap using
--with-long-double-format=ieee (and LIBDRUNTIME_ONLY=yes removed) completed
with no errors and this is my gdc testsuite results, which looks pretty good to
me (ie, vast majority of gdc tests pass). I can look into the few errors here,
but after I look into the IBM128 default system build issue.
=== gdc tests ===
Running target unix
FAIL: gdc.dg/Wbuiltin_declaration_mismatch1.d (test for warnings, line 10)
FAIL: gdc.dg/torture/gdc309.d -O0 execution test
FAIL: gdc.dg/torture/gdc309.d -O0 -g execution test
FAIL: gdc.dg/torture/gdc309.d -O1 execution test
FAIL: gdc.dg/torture/gdc309.d -O1 -g execution test
FAIL: gdc.dg/torture/gdc309.d -O2 execution test
FAIL: gdc.dg/torture/gdc309.d -O2 -g execution test
FAIL: gdc.dg/torture/gdc309.d -O3 execution test
FAIL: gdc.dg/torture/gdc309.d -O3 -g execution test
FAIL: gdc.dg/torture/gdc309.d -Os execution test
FAIL: gdc.dg/torture/gdc309.d -Os -g execution test
UNRESOLVED: gdc.test/runnable/constfold.d compilation failed to produce
executable
UNRESOLVED: gdc.test/runnable/constfold.d -shared-libphobos compilation
failed to produce executable
FAIL: gdc.test/runnable/xtest46.d execution test
FAIL: gdc.test/runnable/xtest46.d -shared-libphobos execution test
FAIL: gdc.test/runnable/xtest46_gc.d execution test
FAIL: gdc.test/runnable/xtest46_gc.d -shared-libphobos execution test
=== gdc Summary ===
# of expected passes 11442
# of unexpected failures 15
# of unresolved testcases 2
# of unsupported tests 442
/home/bergner/gcc/build/gcc-fsf-master-lang-D/gcc/gdc version 13.0.0 20220916
(experimental) (GCC)
next prev parent reply other threads:[~2022-09-16 18:35 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 [this message]
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-mkV8Aj5oJy@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).