public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug libc/26558] New: [meta] Build glibc with LLD
@ 2020-08-31 23:19 i at maskray dot me
2020-08-31 23:31 ` [Bug libc/26558] " i at maskray dot me
` (5 more replies)
0 siblings, 6 replies; 7+ messages in thread
From: i at maskray dot me @ 2020-08-31 23:19 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=26558
Bug ID: 26558
Summary: [meta] Build glibc with LLD
Product: glibc
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: i at maskray dot me
CC: drepper.fsp at gmail dot com
Target Milestone: ---
Some known issues:
* elf/librtld.map.o uses a subtle property of --defsym:
https://sourceware.org/pipermail/libc-alpha/2020-April/112732.html
* ld.lld --verbose does not print a linker script and ld.lld
--print-output-format is not supported:
https://sourceware.org/pipermail/libc-alpha/2020-April/112733.html
* Neither clang nor LLD may support the semantics of .tls_common
https://sourceware.org/pipermail/libc-alpha/2020-April/112734.html
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 7+ messages in thread* [Bug libc/26558] [meta] Build glibc with LLD 2020-08-31 23:19 [Bug libc/26558] New: [meta] Build glibc with LLD i at maskray dot me @ 2020-08-31 23:31 ` i at maskray dot me 2020-09-01 12:41 ` hjl.tools at gmail dot com ` (4 subsequent siblings) 5 siblings, 0 replies; 7+ messages in thread From: i at maskray dot me @ 2020-08-31 23:31 UTC (permalink / raw) To: glibc-bugs https://sourceware.org/bugzilla/show_bug.cgi?id=26558 Fangrui Song <i at maskray dot me> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |26559 Referenced Bugs: https://sourceware.org/bugzilla/show_bug.cgi?id=26559 [Bug 26559] Get OUTPUT_FORMAT from objdump -f to support LLD -- You are receiving this mail because: You are on the CC list for the bug. ^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug libc/26558] [meta] Build glibc with LLD 2020-08-31 23:19 [Bug libc/26558] New: [meta] Build glibc with LLD i at maskray dot me 2020-08-31 23:31 ` [Bug libc/26558] " i at maskray dot me @ 2020-09-01 12:41 ` hjl.tools at gmail dot com 2020-09-01 13:08 ` hjl.tools at gmail dot com ` (3 subsequent siblings) 5 siblings, 0 replies; 7+ messages in thread From: hjl.tools at gmail dot com @ 2020-09-01 12:41 UTC (permalink / raw) To: glibc-bugs https://sourceware.org/bugzilla/show_bug.cgi?id=26558 H.J. Lu <hjl.tools at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2020-09-01 Ever confirmed|0 |1 --- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> --- (In reply to Fangrui Song from comment #0) > Some known issues: > > * elf/librtld.map.o uses a subtle property of --defsym: > https://sourceware.org/pipermail/libc-alpha/2020-April/112732.html Since --defsym in ldd is incompatible with glibc build, --defsym should be poisoned for glibc build. > * ld.lld --verbose does not print a linker script and ld.lld > --print-output-format is not supported: > https://sourceware.org/pipermail/libc-alpha/2020-April/112733.html > * Neither clang nor LLD may support the semantics of .tls_common > https://sourceware.org/pipermail/libc-alpha/2020-April/112734.html This is used to implement STT_COMMON. Do clang/LLD support STT_COMMON? -- You are receiving this mail because: You are on the CC list for the bug. ^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug libc/26558] [meta] Build glibc with LLD 2020-08-31 23:19 [Bug libc/26558] New: [meta] Build glibc with LLD i at maskray dot me 2020-08-31 23:31 ` [Bug libc/26558] " i at maskray dot me 2020-09-01 12:41 ` hjl.tools at gmail dot com @ 2020-09-01 13:08 ` hjl.tools at gmail dot com 2020-09-01 14:25 ` hjl.tools at gmail dot com ` (2 subsequent siblings) 5 siblings, 0 replies; 7+ messages in thread From: hjl.tools at gmail dot com @ 2020-09-01 13:08 UTC (permalink / raw) To: glibc-bugs https://sourceware.org/bugzilla/show_bug.cgi?id=26558 --- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> --- I think you should make your glibc branch for lld available so that people can give it a try. -- You are receiving this mail because: You are on the CC list for the bug. ^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug libc/26558] [meta] Build glibc with LLD 2020-08-31 23:19 [Bug libc/26558] New: [meta] Build glibc with LLD i at maskray dot me ` (2 preceding siblings ...) 2020-09-01 13:08 ` hjl.tools at gmail dot com @ 2020-09-01 14:25 ` hjl.tools at gmail dot com 2021-09-06 4:40 ` i at maskray dot me 2021-09-06 4:41 ` i at maskray dot me 5 siblings, 0 replies; 7+ messages in thread From: hjl.tools at gmail dot com @ 2020-09-01 14:25 UTC (permalink / raw) To: glibc-bugs https://sourceware.org/bugzilla/show_bug.cgi?id=26558 H.J. Lu <hjl.tools at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hjl.tools at gmail dot com --- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> --- Before lld can be accepted for glibc build, it must generate the same set of failures in glibc testsuite with binutils 2.35 at least on i686 and x86-64. -- You are receiving this mail because: You are on the CC list for the bug. ^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug libc/26558] [meta] Build glibc with LLD 2020-08-31 23:19 [Bug libc/26558] New: [meta] Build glibc with LLD i at maskray dot me ` (3 preceding siblings ...) 2020-09-01 14:25 ` hjl.tools at gmail dot com @ 2021-09-06 4:40 ` i at maskray dot me 2021-09-06 4:41 ` i at maskray dot me 5 siblings, 0 replies; 7+ messages in thread From: i at maskray dot me @ 2021-09-06 4:40 UTC (permalink / raw) To: glibc-bugs https://sourceware.org/bugzilla/show_bug.cgi?id=26558 Bug 26558 depends on bug 26559, which changed state. Bug 26559 Summary: Get OUTPUT_FORMAT from objdump -f to support LLD https://sourceware.org/bugzilla/show_bug.cgi?id=26559 What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug. ^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug libc/26558] [meta] Build glibc with LLD 2020-08-31 23:19 [Bug libc/26558] New: [meta] Build glibc with LLD i at maskray dot me ` (4 preceding siblings ...) 2021-09-06 4:40 ` i at maskray dot me @ 2021-09-06 4:41 ` i at maskray dot me 5 siblings, 0 replies; 7+ messages in thread From: i at maskray dot me @ 2021-09-06 4:41 UTC (permalink / raw) To: glibc-bugs https://sourceware.org/bugzilla/show_bug.cgi?id=26558 Fangrui Song <i at maskray dot me> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #4 from Fangrui Song <i at maskray dot me> --- Fixed by https://sourceware.org/git/?p=glibc.git;a=commit;h=224edada607ebc6aaa1aadaae423128fae7880df ("configure: Allow LD to be LLD 13.0.0 or above [BZ #26558]") Target: 2.35 -- You are receiving this mail because: You are on the CC list for the bug. ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2021-09-06 4:41 UTC | newest] Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2020-08-31 23:19 [Bug libc/26558] New: [meta] Build glibc with LLD i at maskray dot me 2020-08-31 23:31 ` [Bug libc/26558] " i at maskray dot me 2020-09-01 12:41 ` hjl.tools at gmail dot com 2020-09-01 13:08 ` hjl.tools at gmail dot com 2020-09-01 14:25 ` hjl.tools at gmail dot com 2021-09-06 4:40 ` i at maskray dot me 2021-09-06 4:41 ` i at maskray dot me
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).