[Bug libgcc/106949] Memory leak using VLA with -fsplit-stack

2022-10-03 Thread ian at airs dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106949 --- Comment #3 from Ian Lance Taylor --- I don't think your attached patch is going to work. The code assumes that it is running within a stack segment. You can't just add a stack segment without changing the stack pointer. But something like

[Bug libgcc/106949] Memory leak using VLA with -fsplit-stack

2022-10-03 Thread iam at datacompboy dot ru via Gcc-bugs
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.

[Bug libgcc/106949] Memory leak using VLA with -fsplit-stack

2022-09-15 Thread iam at datacompboy dot ru via Gcc-bugs
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. */