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 libc/27492] Make static linking friendly with {ld.bfd,ld.lld} -z start-stop-gc: removing unused section '__libc_atexit'
Date: Tue, 02 Mar 2021 05:16:37 +0000	[thread overview]
Message-ID: <bug-27492-131-GjxTKUGzjr@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27492-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27492

--- Comment #2 from Fangrui Song <i at maskray dot me> ---
The quickest fix is probably

- *(__libc_atexit)
+ KEEP(*(__libc_atexit))

A better fix is to add a R_*_NONE relocation (`.reloc ., R_X86_64_NONE,
target`) from the use site to a symbol in the __libc_atexit section.
Unfortunately the .reloc approach needs to hard code the relocation name on
various targets.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-03-02  5:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-01  8:37 [Bug libc/27492] New: " i at maskray dot me
2021-03-01 13:54 ` [Bug libc/27492] " fweimer at redhat dot com
2021-03-02  5:16 ` i at maskray dot me [this message]
2021-04-17  3:09 ` i at maskray dot me

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-27492-131-GjxTKUGzjr@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: 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 read-only IMAP folder(s) and NNTP newsgroup(s).