public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/31317] New: [RISCV] static PIE crashes during self relocation Date: Tue, 30 Jan 2024 13:25:27 +0000 [thread overview] Message-ID: <bug-31317-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31317 Bug ID: 31317 Summary: [RISCV] static PIE crashes during self relocation Product: glibc Version: 2.39 Status: NEW Severity: normal Priority: P2 Component: dynamic-link Assignee: unassigned at sourceware dot org Reporter: schwab@linux-m68k.org Target Milestone: --- When running a static PIE created by the mold linker, it crashes during self relocation while it tries to look up the __global_pointer$ symbols. That happens because the mold linker puts the relocation addend of a RELATIVE also in the relocated field (unlike the BFD linker, which sets it to zero). From sysdeps/riscv/dl-machine.h: if (l->l_type == lt_executable && l->l_scope != NULL) In elf_machine_runtime_setup the condition l->l_scope != NULL references an unrelocated pointer (where l points to the statically initialized _dl_main_map) which is never NULL in a static PIE produced by ld.mold. The failure can be seen in the mold testsuite (riscv64-ifunc-static-pie and riscv64-static-pie). https://build.opensuse.org/package/live_build_log/devel:gcc:next/mold/openSUSE_Factory_RISCV/riscv64 -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-01-30 13:25 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-30 13:25 schwab@linux-m68k.org [this message] 2024-02-22 18:44 ` [Bug dynamic-link/31317] " palmer at gcc dot gnu.org 2024-02-22 21:47 ` schwab@linux-m68k.org 2024-02-22 22:53 ` palmer at gcc dot gnu.org 2024-02-22 23:01 ` vineet.gupta at linux dot dev 2024-02-22 23:16 ` schwab@linux-m68k.org 2024-02-22 23:26 ` palmer at gcc dot gnu.org 2024-02-23 3:06 ` yanzhang.wang at intel dot com 2024-03-06 14:44 ` rjones at redhat dot com 2024-03-25 14:20 ` cvs-commit at gcc dot gnu.org 2024-03-26 13:47 ` schwab@linux-m68k.org 2024-10-13 17:07 ` cyy at cyyself dot name
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-31317-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).