public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "i at maskray dot me" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/28154] New: [test] sysdeps/x86/tst-ifunc-isa-* lazy binding failure with ld.lld Date: Wed, 28 Jul 2021 21:15:18 +0000 [thread overview] Message-ID: <bug-28154-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=28154 Bug ID: 28154 Summary: [test] sysdeps/x86/tst-ifunc-isa-* lazy binding failure with ld.lld Product: glibc Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: dynamic-link Assignee: unassigned at sourceware dot org Reporter: i at maskray dot me Target Milestone: --- Extracted from https://sourceware.org/pipermail/libc-alpha/2021-July/129450.html To build LLD 13.0.0: # https://github.com/llvm/llvm-project/ origin/release/13.x cmake -H. -Bout/release -G Ninja -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_PROJECTS='clang;lld' ninja -C out/release lld I use sudo ln -sf $PWD/out/release/bin/lld /usr/local/bin/ld to ensure the glibc build system definitely picks ld => lld (messing around with LDFLAGS=-fuse-ld=lld may work as well) `make check` says sysdeps/x86/tst-ifunc-isa-* fail. The tests work with LD_BIND_NOW=1. I debugged a bit. ld.lld and GNU ld place IRELATIVE differently. IIUC some ports of GNU ld use .rela.dyn and behave similar to ld.lld. The tests happen to work with GNU ld because the IRELATIVE for foo_ifunc is placed after JUMP_SLOT in .repa.plt. The test needs to call __x86_get_cpuid_feature_leaf which is defined in a different TU. IMHO such ifunc does not guaranteed to work. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-07-28 21:15 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-28 21:15 i at maskray dot me [this message] 2021-07-29 22:21 ` [Bug dynamic-link/28154] " hjl.tools at gmail dot com 2021-07-29 22:54 ` i at maskray dot me 2021-07-29 23:07 ` hjl.tools at gmail dot com 2021-09-01 5:43 ` cvs-commit at gcc dot gnu.org 2024-04-24 7:10 ` amodra at gmail dot com
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-28154-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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: linkBe 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).