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 1F99F3858D20; Mon, 15 Jan 2024 16:50:13 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1F99F3858D20
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1705337413;
	bh=r2Je1fOD4dD9oOz3h3dtTNdIvHVqFv4wG17GShHpg2U=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=TWLZDWK0EQAr75f/dBaGRxdAXdhievGnza9O52yurfw04YE0qAthA2gJ6GTVnkk4O
	 AMlbTR97kNnauSqyhXaPm9vtCLnIq+z+L0DeJK6Kd5PRD5RBgRkmbBcyF2JrZZFQxt
	 7WAWIS0GrCDOmnWOEgRw+q4L699OgF9/AtL2TltE=
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/113401] Memory (resource) leak in -ftrampoline-impl=heap
Date: Mon, 15 Jan 2024 16:50:12 +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: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-113401-4-BtsKvq9vS9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113401-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113401-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=3D113401

Iain Sandoe <iains at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |iains at gcc dot gnu.org

--- Comment #1 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Florian Weimer from comment #0)

> The fix is to register a TLS destructor to
> deallocate that page, too. On glibc, that also fixes another memory leak =
for
> -fno-exceptions compilations (the default for C) if pthread_exit is called
> with an active trampoline.

Does this mean you have a proposed patch already? (before I start
investigation)=