public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
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 [thread overview] Message-ID: <bug-106949-4-OYS01BICkP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106949-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106949 --- 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...
prev parent reply other threads:[~2022-10-04 15:50 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-15 8:18 [Bug libgcc/106949] New: Memory leak using VLA " iam at datacompboy dot ru 2022-09-15 8:21 ` [Bug libgcc/106949] " iam at datacompboy dot ru 2022-10-03 12:25 ` iam at datacompboy dot ru 2022-10-04 0:22 ` ian at airs dot com 2022-10-04 12:16 ` [Bug libgcc/106949] Memory leak using VLA/alloca " iam at datacompboy dot ru 2022-10-04 15:50 ` iam at datacompboy dot ru [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-106949-4-OYS01BICkP@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).