public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/113403] __builtin_nested_func_ptr_created, __builtin_nested_func_ptr should be dynamically linked by default Date: Mon, 15 Jan 2024 21:36:02 +0000 [thread overview] Message-ID: <bug-113403-4-NcCNKymYES@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113403-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113403 Jason Merrill <jason at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jason at gcc dot gnu.org --- Comment #6 from Jason Merrill <jason at gcc dot gnu.org> --- This seems somewhat similar to the C++ issue that led to introducing STB_GNU_UNIQUE; a DSO keeping its own copy of something that we want to be shared. In the C++ case we were dealing with vague linkage variables that we have no control over, and decided that the first copy that gets loaded is used by all later DSOs, and so it can never be unloaded. Here, we have more control over the definition, and could say that everyone should get it from libgcc_s, as Jakub proposes. Or we could force it to be defined in the executable, so all DSOs will use the copy there. That latter might be another way to handle the STB_GNU_UNIQUE situation: if an executable links against a shared library that defines something STB_GNU_UNIQUE, copy the definition from the library into the executable? That would avoid the dlclose problem.
next prev parent reply other threads:[~2024-01-15 21:36 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-15 16:42 [Bug libgcc/113403] New: " fw at gcc dot gnu.org 2024-01-15 17:07 ` [Bug libgcc/113403] " iains at gcc dot gnu.org 2024-01-15 17:11 ` fw at gcc dot gnu.org 2024-01-15 17:24 ` iains at gcc dot gnu.org 2024-01-15 17:46 ` jakub at gcc dot gnu.org 2024-01-15 20:13 ` iains at gcc dot gnu.org 2024-01-15 21:36 ` jason at gcc dot gnu.org [this message] 2024-01-16 8:04 ` [Bug libgcc/113403] [14 Regression] " rguenth at gcc dot gnu.org 2024-01-16 9:00 ` fw at gcc dot gnu.org 2024-01-16 9:06 ` jakub at gcc dot gnu.org 2024-01-16 9:15 ` iains at gcc dot gnu.org 2024-01-16 9:22 ` jakub at gcc dot gnu.org 2024-01-16 11:12 ` fw at gcc dot gnu.org 2024-01-16 11:21 ` iains at gcc dot gnu.org 2024-01-21 23:37 ` iains at gcc dot gnu.org 2024-01-30 9:33 ` cvs-commit at gcc dot gnu.org 2024-01-30 9:33 ` cvs-commit at gcc dot gnu.org 2024-01-30 19:03 ` jakub at gcc dot gnu.org 2024-02-01 20:10 ` cvs-commit at gcc dot gnu.org
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-113403-4-NcCNKymYES@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).