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 DF05F385840C; Tue,  4 Oct 2022 15:50:14 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DF05F385840C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1664898614;
	bh=I7y+QdoKY/1upYlSZvVa0IdKcVl+JrgXJHzRKcQQUg4=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=dvJnBOkLlZ4bm3ge6Qe5Sxv3nn3gusAXx6Rp4pVe74AXLY5f5gCfxKkUGXKkLeP1t
	 y4I0dtywyBjflmq7hIY9wwa1GWGwjvHzrqrGYpBitQb9uIS8wot+RmhBYF7YIcnLRm
	 AP6ktK++T0txqcasGOGYd5L0fEf8Bp+rE5mdrZMA=
From: "iam at datacompboy dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/106949] Memory leak using VLA/alloca with -fsplit-stack
Date: Tue, 04 Oct 2022 15:50:14 +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: 13.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iam at datacompboy dot ru
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: 
Message-ID: <bug-106949-4-OYS01BICkP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-106949-4@http.gcc.gnu.org/bugzilla/>
References: <bug-106949-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=3D106949

--- Comment #5 from Anton Fedorov <iam at datacompboy dot ru> ---
Hhhhmmm... Interesting, it doesn't seems to be possible, but it would be fun
way to fix to add cleanup(free) attribute to the variable if it has to be
malloc'ed...=