public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105265] [9/10/11/12 Regression] temporary object not destructed causing memory leaks Date: Wed, 13 Apr 2022 15:10:28 +0000 [thread overview] Message-ID: <bug-105265-4-VEXru6YYXS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105265-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105265 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail|12.0 | Known to work| |12.0 --- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> --- Ah yes, it was fixed by r12-1165
next prev parent reply other threads:[~2022-04-13 15:10 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-13 14:01 [Bug c++/105265] New: " jack.cui2 at foxmail dot com 2022-04-13 14:15 ` [Bug c++/105265] " jack.cui2 at foxmail dot com 2022-04-13 14:23 ` jack.cui2 at foxmail dot com 2022-04-13 14:48 ` [Bug c++/105265] [9/10/11/12 Regression] " redi at gcc dot gnu.org 2022-04-13 15:09 ` ppalka at gcc dot gnu.org 2022-04-13 15:10 ` redi at gcc dot gnu.org [this message] 2022-04-13 15:14 ` [Bug c++/105265] [9/10/11 " redi at gcc dot gnu.org 2022-04-13 15:25 ` ppalka at gcc dot gnu.org 2022-04-13 16:13 ` jason at gcc dot gnu.org 2022-04-13 16:17 ` jason at gcc dot gnu.org 2022-04-14 0:22 ` cvs-commit at gcc dot gnu.org 2022-04-14 6:31 ` rguenth at gcc dot gnu.org 2022-05-12 20:14 ` cvs-commit at gcc dot gnu.org 2022-05-12 21:24 ` [Bug c++/105265] [9/10 " cvs-commit at gcc dot gnu.org 2022-05-13 18:24 ` [Bug c++/105265] [9 " cvs-commit at gcc dot gnu.org 2022-05-13 18:26 ` jason 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-105265-4-VEXru6YYXS@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).