https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106949
--- Comment #5 from Anton Fedorov ---
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...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106949
--- Comment #4 from Anton Fedorov ---
> You can't just add a stack segment without changing the stack pointer.
I can -- since we are on the initial stack at this point, no return into
__morestack will happen so no attempt to release it, thus th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106949
--- Comment #2 from Anton Fedorov ---
Created attachment 53654
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53654&action=edit
potential fix
I checked with the HEAD (43faf3e5445b571731e52faa1be085ecd0a09323) and the
issue is still there.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106949
--- Comment #1 from Anton Fedorov ---
Dunno, is this related to this point?
https://github.com/gcc-mirror/gcc/blob/master/libgcc/generic-morestack.c#L796
/* If we are still on the initial stack, then we have a space leak.
FIXME. */
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106949
Bug ID: 106949
Summary: Memory leak using VLA with -fsplit-stack
Product: gcc
Version: 11.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libgc
