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 9A5C03858D38; Tue, 16 Jan 2024 09:01:02 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9A5C03858D38
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1705395663;
	bh=HGmYGqs2O9xZOrInjVDeSFZyXj/1v3IhKPONHEsuX6c=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=jYNQIbxDd4NDruxzGiiH4J/5z8CMPtKnQSRTMa6RxKuJhER+uyvb7UJzpVyhiHtiC
	 f8St7cEgg8I/SABsE4WIZdu1QgR37xr0tbt5g7jve5FhJwqMc9grYbEOS1Eoq9wmP3
	 u0WWSZ9uTSv4TDQSamn4HvpT1VpGN17jXdmn0yEQ=
From: "fw 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 09:00:53 +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: fw 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-R7WJpE5KGl@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 #8 from Florian Weimer <fw at gcc dot gnu.org> ---
In the current implementation, as far as I understand it, avoiding multiple
objects is just an optimization, not a correctness issue. STB_GNU_UNIQUE is=
 for
correctness (although I don't think we'd implement it this way today).

The deallocation API does not explicitly reference the closure, which is why
stackful coroutines/fibers will have to switch the allocator state as part =
of
the context switch. Once we start doing this, it simplifies matters greatly=
 if
there is just one such state to switch, and not an arbitrary count.=