public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/113401] Memory (resource) leak in -ftrampoline-impl=heap Date: Mon, 22 Jan 2024 10:21:39 +0000 [thread overview] Message-ID: <bug-113401-4-7bcFFpBb3L@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113401-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113401 --- Comment #6 from Florian Weimer <fw at gcc dot gnu.org> --- Sorry, pthread_cleanup_push is purely scope-based, like the existing handler. It cannot be used to push a handler to some unscoped cleanup function list that persists even after the current function returns. It's also implemented as a macro, so it's not possible to emit it from builtin expansion.
next prev parent reply other threads:[~2024-01-22 10:21 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-15 16:35 [Bug target/113401] New: " fw at gcc dot gnu.org 2024-01-15 16:50 ` [Bug libgcc/113401] " iains at gcc dot gnu.org 2024-01-15 16:54 ` fw at gcc dot gnu.org 2024-01-21 23:42 ` iains at gcc dot gnu.org 2024-01-22 9:57 ` fw at gcc dot gnu.org 2024-01-22 10:11 ` iains at gcc dot gnu.org 2024-01-22 10:21 ` fw at gcc dot gnu.org [this message] 2024-01-22 10:27 ` iains at gcc dot gnu.org 2024-01-22 10:31 ` fw at gcc dot gnu.org 2024-01-22 10:46 ` iains at gcc dot gnu.org
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-113401-4-7bcFFpBb3L@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).