public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains 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, 16 Jan 2024 11:21:21 +0000	[thread overview]
Message-ID: <bug-113403-4-Esu4Grxg91@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 #13 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Florian Weimer from comment #12)
> (In reply to Jakub Jelinek from comment #11)
> > Or put it in libgcc_eh.a and libgcc_s.so.1?
> 
> Yes, that's what I came up with as well (conceptually, not a patch, and I
> only have a background in ELF), but Iain already dismissed it in comment 3.

I would not do that for Darwin, experience with emuTLS gave us headaches in
doing that, especially since our users are often building projects using both
GCC and clang.

However, this is an area where individual targets can have different solutions
- so my comment should not be seen to apply to ELF targets if that seems the
best remedy there.

  parent reply	other threads:[~2024-01-16 11:21 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 [this message]
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-Esu4Grxg91@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: 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).