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 7957C3858C74; Thu, 15 Sep 2022 08:21:50 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7957C3858C74
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1663230110;
	bh=3U51ondtcv/OKs+iwZuPpD7Y3B5psuZTgC7QiJfCXqI=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=jEwMY3nN3jmMXLLr9cw75D2pbsGRCrVzWRSp47tVLsnLBQWO7n1DlAZOVCzeDxH2v
	 uf+3+r0/IjVMPPvpmnEymsmttyy9nQa69XrhPlCE03HzRjPdt1fq7zI5WXWy2AH5ny
	 ml82lNwrbZfDhJUxTHZ6jjnDSPBUYDblwaE1RdGg=
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 with -fsplit-stack
Date: Thu, 15 Sep 2022 08:21:50 +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: 11.2.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-0kn4mpQizZ@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 #1 from Anton Fedorov <iam at datacompboy dot ru> ---
Dunno, is this related to this point?
https://github.com/gcc-mirror/gcc/blob/master/libgcc/generic-morestack.c#L7=
96

  /* If we are still on the initial stack, then we have a space leak.
     FIXME.  */=