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: Wed, 15 Dec 2021 09:25:41 +0000 [thread overview]
Message-ID: <bug-103577-4-qeYj1HRr3o@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 #6 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #5 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot
> Uni-Bielefeld.DE> ---
>> --- Comment #3 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
>> FYI, with darwin, I've only been using the most recent commit in
>> releases/gcc-11 for testing as there have been a number of issues exposed from
>> that port.
>>
>> I have VMs set-up running 10.4 (PPC), 10.6 (x86_64), 10.13, 10.14, 10.15, 11,
>> and 12. Not yet gotten round to building a bootstrap compiler from gcc-11 just
>> yet though for testing build of master.
>
> Good to know. Once the gcc-11 builds are done, I'll retry bootstrapping
> master on 10.7 and 12. Maybe the SEGVs on 10.7 stage1 will be gone that
> way...
I've now done just that:
* build top of gcc-11 with --enable-languages=d --enable-libphobos
* use that as bootstrap gdc for master
Results are pretty good:
* The corrupted *.Po files in stage1 are gone.
* On 10.7, the d21 SEGV is gone
* gdc and libphobos testsuite results on both 10.7 and 12 are
reasonable.
There's one caveat, though:
On 10.7 (so far), a couple of files don't compile building stage2 libphobos:
dyld: Symbol not found: __D6object10_xopEqualsFxPvxQdZb
Referect10_xopEqualsFxPvxQdZb
Referenced from: /var/gcc/regression/mnced from:
/var/gcc/regression/master/10.7-gcc/build/./gcc/d21
Expected in:
/var/gcc/regression/master/10.7-gcc/build/x86_64-apple-darwin11.4.2/libphobos/src/.libs/libgphobos.2.dylib
in
/var/gcc/regression/master/10.7-gcc/gcc/regression/master/10.7-gcc/build/./gcc/d21
and indeed that symbol (object._xopEquals(const(void*), const(void*)))
is missing from the freshly built libgphobos, while it is present in the
gcc-11 one.
I suspect this happens because the toplevel Makefile sets
DYLD_LIBRARY_PATH, since when I just run make in
x86_64-apple-darwin11.4.2/libphobos, the build succeeds without further
problems.
There are two issues here, I believe:
* The one line patch to gcc/config/darwin.h to support -static-libphobos
should be backported to the gcc-11 branch to avoid this in the first
place.
* Besides, making incompatible changes to libgphobos (like removing an
exported interface) shouldn't be done without increasing the library
version number.
prev parent reply other threads:[~2021-12-15 9:25 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 ` [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 [this message]
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-qeYj1HRr3o@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).