public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/113403] [14 Regression] __builtin_nested_func_ptr_created, __builtin_nested_func_ptr should be dynamically linked by default Date: Tue, 30 Jan 2024 09:33:22 +0000 [thread overview] Message-ID: <bug-113403-4-KejnFL3pEO@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 --- Comment #16 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Iain D Sandoe <iains@gcc.gnu.org>: https://gcc.gnu.org/g:506e74f53a5e4f607284d3c41da17cdd3eca4fb8 commit r14-8521-g506e74f53a5e4f607284d3c41da17cdd3eca4fb8 Author: Iain Sandoe <iain@sandoe.co.uk> Date: Sun Jan 28 13:31:56 2024 +0000 libgcc: Make heap trampoline support dynamic [PR113403]. In order to handle system security constraints during GCC build and test and that most platform versions cannot link to libgcc_eh since the unwinder there is incompatible with the system one. 1. We make the support functions weak definitions. 2. We include them as a CRT for platform conditions that do not allow libgcc_eh. 3. We ensure that the weak symbols are exported from DSOs (which includes exes on Darwin) so that the dynamic linker will pick one instance (which avoids duplication of trampoline caches). PR libgcc/113403 gcc/ChangeLog: * config/darwin.h (DARWIN_SHARED_WEAK_ADDS, DARWIN_WEAK_CRTS): New. (REAL_LIBGCC_SPEC): Move weak CRT handling to separate spec. * config/i386/darwin.h (DARWIN_HEAP_T_LIB): New. * config/i386/darwin32-biarch.h (DARWIN_HEAP_T_LIB): New. * config/i386/darwin64-biarch.h (DARWIN_HEAP_T_LIB): New. * config/rs6000/darwin.h (DARWIN_HEAP_T_LIB): New. libgcc/ChangeLog: * config.host: Build libheap_t.a for i686/x86_64 Darwin. * config/aarch64/heap-trampoline.c (HEAP_T_ATTR): New. (allocate_tramp_ctrl): Allow a target to build this as a weak def. (__gcc_nested_func_ptr_created): Likewise. * config/i386/heap-trampoline.c (HEAP_T_ATTR): New. (allocate_tramp_ctrl): Allow a target to build this as a weak def. (__gcc_nested_func_ptr_created): Likewise. * config/t-darwin: Build libheap_t.a (a CRT with heap trampoline support).
next prev parent reply other threads:[~2024-01-30 9:33 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 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 [this message] 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-KejnFL3pEO@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).