From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [TRACKING] gcc 12 build failures
Date: Mon, 05 Dec 2022 06:02:25 +0100 [thread overview]
Message-ID: <20221205050225.MaP2y---nEAWb17h05omRiyfkf3nNo9iabg3Ap71yGM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39809@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2235 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/39809#issuecomment-1336554579
Comment:
The ldc build failure seems to be a segfault in ldc2.
Even after updating it still crashes.
The crash location I got was:
https://github.com/ldc-developers/ldc/blob/master/gen/target.cpp#L180
```
Program received signal SIGSEGV, Segmentation fault.
Target::_init (this=0xbc7d78 <target>, params=...) at /builddir/ldc-1.30.0/gen/target.cpp:180
180 RealProperties.min_10_exp = -4931;
(gdb)
(gdb) bt
#0 Target::_init (this=0xbc7d78 <target>, params=...)
at /builddir/ldc-1.30.0/gen/target.cpp:180
#1 0x000000000081acfd in mars_mainBody(Param&, Array<char const*>&, Array<char const*>&) (params=..., files=..., libmodules=...)
at /builddir/ldc-1.30.0/dmd/mars.d:336
#2 0x00000000009d1f0e in cppmain ()
at /builddir/ldc-1.30.0/driver/main.cpp:1148
#3 0x000000000091a04d in _Dmain (_param_0=...)
at /builddir/ldc-1.30.0/driver/main.d:27
```
Here is a snippet of the disas:
```
...
0x000000000095e6ca <+1402>: xor %esi,%esi
0x000000000095e6cc <+1404>: mov $0xaaf859,%edi
0x000000000095e6d1 <+1409>: fstpt 0x180(%rbx)
0x000000000095e6d7 <+1415>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6dc <+1420>: xor %esi,%esi
0x000000000095e6de <+1422>: mov $0xaaf864,%edi
0x000000000095e6e3 <+1427>: fstpt 0x190(%rbx)
0x000000000095e6e9 <+1433>: call 0x913210 <_ZN7CTFloat5parseEPKcPb>
0x000000000095e6ee <+1438>: movdqa 0x15138a(%rip),%xmm0 # 0xaafa80
0x000000000095e6f6 <+1446>: fstpt 0x1c0(%rbx)
=> 0x000000000095e6fc <+1452>: movaps %xmm0,0x1d0(%rbx)
```
I assume this has to do with LLVM and libstdc++, alpine uses LLVM 14 which we don't have so I can't test it. The build failure also occurs with clang/clang++ and libstdc++ although when I try to build it with libc++ I get a bunch of undefined references to LLVM.
Also, sidenote but libexecinfo is broken on musl:
https://github.com/alpinelinux/aports/commit/50795a14dee639ce2dcc836e2b2baca9bad4a1b1
Although removing it/stubbing it out didn't fix the issue it did stop libexecinfo from messing up the gdb backtrace.
next prev parent reply other threads:[~2022-12-05 5:02 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-08 13:16 [ISSUE] " Duncaen
2022-10-08 21:08 ` oreo639
2022-10-08 21:08 ` oreo639
2022-10-08 21:08 ` oreo639
2022-10-09 18:22 ` Anachron
2022-10-09 18:26 ` Duncaen
2022-10-09 21:28 ` oreo639
2022-10-09 23:15 ` oreo639
2022-10-10 14:48 ` dkwo
2022-10-15 9:44 ` oreo639
2022-10-15 10:41 ` oreo639
2022-10-15 12:54 ` oreo639
2022-10-15 12:54 ` oreo639
2022-10-19 7:40 ` oreo639
2022-10-19 7:41 ` oreo639
2022-10-19 7:41 ` oreo639
2022-10-19 7:52 ` oreo639
2022-10-19 8:02 ` oreo639
2022-10-31 17:29 ` dkwo
2022-12-04 23:51 ` oreo639
2022-12-05 0:57 ` oreo639
2022-12-05 1:00 ` oreo639
2022-12-05 1:02 ` oreo639
2022-12-05 3:02 ` oreo639
2022-12-05 3:03 ` oreo639
2022-12-05 3:17 ` oreo639
2022-12-05 3:19 ` oreo639
2022-12-05 4:58 ` oreo639
2022-12-05 4:59 ` oreo639
2022-12-05 5:01 ` oreo639
2022-12-05 5:02 ` oreo639 [this message]
2022-12-05 18:56 ` oreo639
2022-12-05 18:57 ` oreo639
2022-12-06 1:32 ` oreo639
2022-12-06 2:46 ` oreo639
2022-12-06 2:46 ` oreo639
2022-12-18 3:47 ` oreo639
2023-06-21 16:16 ` [ISSUE] [CLOSED] " Duncaen
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=20221205050225.MaP2y---nEAWb17h05omRiyfkf3nNo9iabg3Ap71yGM@z \
--to=oreo639@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).