From: Rich Felker <dalias@libc.org>
To: Jiahao XU <Jiahao_XU@outlook.com>
Cc: musl@lists.openwall.com
Subject: Re: [musl] Can’t build musl with lto=thin
Date: Sat, 30 Jan 2021 18:30:12 -0500 [thread overview]
Message-ID: <20210130233012.GR23432@brightrain.aerifal.cx> (raw)
In-Reply-To: <SYBP282MB020277E08EB49C9AC9BF90888AB89@SYBP282MB0202.AUSP282.PROD.OUTLOOK.COM>
On Sat, Jan 30, 2021 at 11:04:32PM +0000, Jiahao XU wrote:
> > So something like (in config.mak):
> >
> > obj/ldso/dlstart.lo: CFLAGS_ALL += -fno-lto
>
> Thanks, with this I was able to build libc.so successfully with clang and created a 3.5 KB hello world program using clang and lld.
>
> However, I still wasn’t able to statically linked with libc.
>
> Once I added ‘-static’ to the compiler flags, the executable failed with ‘Segmentation fault (core dumped)’.
It's libc.a, not libc.so, that will be involved in making a
static-linked binary. It's hard to know what's going wrong without
more information. Can you run under a debugger and provide a
backtrace, disassembly, and register dump for where the crash occurs?
Rich
> ________________________________
> From: Rich Felker <dalias@libc.org>
> Sent: Sunday, January 31, 2021 7:12:31 AM
> To: Jiahao XU <Jiahao_XU@outlook.com>
> Cc: musl@lists.openwall.com <musl@lists.openwall.com>
> Subject: Re: [musl] Can’t build musl with lto=thin
>
> On Fri, Jan 29, 2021 at 12:19:42PM +0000, Jiahao XU wrote:
> > musl-1.2.2 compilation with clang-11 failed to build libc.so at the final linking stage:
> >
> > ld.lld: error: undefined hidden symbol: __dls2
> > >>> referenced by ld-temp.o
> > >>> lto.tmp:(_dlstart_c)
> > >>> did you mean: __dls3
> > >>> defined in: lto.tmp
> >
> > I am using CFLAGS=‘-march=native -mtune=native -Oz -flto
> > -fmerge-all-constants -fomit-frame-pointer’ and LDFLAGS=‘-flto
> ^^^^^^^^^^^^^^^^^^^^^
>
> The -fmerge-all-constants option gives non-conforming language
> semantics and should not be used, but that's a separate issue.
>
> > -fuse-ld=lld -Wl,—plugin-opt=O3,-O3,—icf=safe’.
>
> > No configure option is supplied.
>
> Otherwise, it's a known issue that LTO misses references from asm
> (both top-level and in functions). I think dlstart.lo and a few other
> files should just be built with LTO disabled; any LTO-type
> optimization in code that runs at this stage is inherently invalid,
> anyway. So something like (in config.mak):
>
> obj/ldso/dlstart.lo: CFLAGS_ALL += -fno-lto
>
> Rich
next prev parent reply other threads:[~2021-01-30 23:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 12:19 Jiahao XU
2021-01-29 20:04 ` Szabolcs Nagy
2021-01-29 20:53 ` Fangrui Song
2021-01-30 20:12 ` Rich Felker
2021-01-30 20:59 ` Леонид Юрьев (Leonid Yuriev)
[not found] ` <SYBP282MB020277E08EB49C9AC9BF90888AB89@SYBP282MB0202.AUSP282.PROD.OUTLOOK.COM>
2021-01-30 23:30 ` Rich Felker [this message]
[not found] ` <SYBP282MB0202BF16DD08A2F1537FD5428AB89@SYBP282MB0202.AUSP282.PROD.OUTLOOK.COM>
2021-01-31 5:01 ` Rich Felker
2021-01-31 5:32 ` Jiahao XU
2021-01-31 21:01 ` Rich Felker
2021-01-31 22:29 ` Jiahao XU
2021-02-01 0:22 ` Jiahao XU
2021-02-01 0:31 ` Jiahao XU
2021-02-01 0:44 ` Jiahao XU
2021-02-01 0:50 ` Jiahao XU
2021-02-01 13:20 ` Jiahao XU
2021-02-01 16:55 ` Nick Bray
2021-02-01 17:53 ` Rich Felker
2021-02-01 18:06 ` Fangrui Song
2021-02-01 21:20 ` Jiahao XU
2021-02-13 17:54 ` Tim Tassonis
2021-02-14 5:59 ` Markus Wichmann
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=20210130233012.GR23432@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=Jiahao_XU@outlook.com \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).