public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/103577] d21 SIGSEGV on Darwin/x86_64
Date: Mon, 13 Dec 2021 12:09:25 +0000 [thread overview]
Message-ID: <bug-103577-4-5ThwWhByyr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103577-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103577
--- Comment #1 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> 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.
FWIW, I recently tried the same procedure in a macOS 12.1 VM
(x86_64-apple-darwin21.2.0). This time, the build succeeded and test
results are reasonable
=== gdc Summary ===
# of expected passes 11587
# of unsupported tests 2
=== libphobos Summary ===
# of expected passes 556
# of unexpected failures 7
# of unsupported tests 1
although I had to rerun the libphobos tests sequentially since several
would time out otherwise.
There's one caveat, though, that applies equally to Mac OS X 10.7 and
macOS 12.1: at least some of the stage1 dependency lists in gcc/d/.deps
are corrupt in that they contain D source code after the dependencies
proper, e.g. gcc/d/.deps/hash.Po:
d/root-hash.o: /vol/gcc/src/hg/master/darwin/gcc/d/dmd/root/hash.d
is.value == c.value;
}
override size_t getHash(scope const void* p) @trusted const
{
return getArrayHash(value, p, len);
}
[...]
I cannot yet tell if this is just an issue with GCC 11.1.0 gdc or
libphobos that's fixed in 11.2.0 or gcc-11 branch.
next prev parent reply other threads:[~2021-12-13 12:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 10:19 [Bug d/103577] New: " ro at gcc dot gnu.org
2021-12-13 12:09 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2021-12-13 12:23 ` [Bug d/103577] " 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-5ThwWhByyr@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).