From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 6524C3858D20; Tue, 16 Jan 2024 11:21:22 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6524C3858D20
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1705404082;
	bh=I0RJuOwYPlQMXqli6+aM0ltm5mA/PeY2W/hnCl8jVAc=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=PWqQduMVcFr1vpTTiFJO2St4eI3GyXwAirLWR4nc4Xl10HfGGwTBdAeqBbFZwgmOR
	 APK9W1XLkx95cE+A76fFGp9saTLS5l8oC4Qn9RCW97257HW392O40iGRLrPmb/nhL+
	 9B8N3vgt5IT0r09iQTI1yJkF5iAooqg3tQkvvlXg=
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgcc
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-113403-4-Esu4Grxg91@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113403-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113403-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113403

--- 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?
>=20
> 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 bo=
th
GCC and clang.

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