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/103577] New: d21 SIGSEGV on Darwin/x86_64
Date: Mon, 06 Dec 2021 10:19:08 +0000 [thread overview]
Message-ID: <bug-103577-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103577
Bug ID: 103577
Summary: d21 SIGSEGV on Darwin/x86_64
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: d
Assignee: ibuclaw at gdcproject dot org
Reporter: ro at gcc dot gnu.org
Target Milestone: ---
Host: x86_64-apple-darwin11.4.2
Target: x86_64-apple-darwin11.4.2
Build: x86_64-apple-darwin11.4.2
I recently tried to build master on Darwin 11 with gcc 11.0.1. That's the
first
release to build gdc, and while libphobos isn't marked as supported in
libphobos/configure.tgt, it does build with --enable-libphobos.
However, with that gdc as bootstrap compiler, the resulting d21 SEGVs building
the stage1 libphobos, e.g.
gdc: internal compiler error: Segmentation fault: 11 signal terminated program
d21
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.
make[5]: *** [core/internal/gc/pooltable.lo] Error 1
Unfortunately, trying to debug d21 with gdb 9.1 just lets gdb hang in
Reading symbols from ./d21...
The bundled lldb fails differently, but provides no information.
I cannot really tell if this is supposed to work in some way or not.
next reply other threads:[~2021-12-06 10:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 10:19 ro at gcc dot gnu.org [this message]
2021-12-13 12:09 ` [Bug d/103577] " ro at CeBiTec dot Uni-Bielefeld.DE
2021-12-13 12:23 ` ibuclaw at gdcproject dot org
2021-12-13 12:26 ` ibuclaw at gdcproject dot org
2021-12-13 12:54 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-12-13 12:56 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-12-15 9:25 ` ro at CeBiTec dot Uni-Bielefeld.DE
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-103577-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: 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).