public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/57111] Generalize -Wfree-nonheap-object to delete Date: Tue, 08 Dec 2020 20:51:11 +0000 [thread overview] Message-ID: <bug-57111-4-1PeNAv242O@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57111-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57111 --- Comment #14 from Martin Sebor <msebor at gcc dot gnu.org> --- The following enables the warning for the test case reported in comment #0 (and all libstdc++ code): https://gcc.gnu.org/pipermail/gcc-patches/2020-December/561378.html
next prev parent reply other threads:[~2020-12-08 20:51 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-29 12:29 [Bug c++/57111] New: Core dump - invalid pointer detected after std::unique_ptr jb.1234abcd at gmail dot com 2013-04-29 12:57 ` [Bug c++/57111] " redi at gcc dot gnu.org 2013-04-29 14:04 ` jb.1234abcd at gmail dot com 2013-04-29 14:09 ` redi at gcc dot gnu.org 2013-04-30 18:37 ` glisse at gcc dot gnu.org 2013-04-30 21:57 ` jb.1234abcd at gmail dot com 2013-04-30 22:07 ` glisse at gcc dot gnu.org 2013-04-30 22:22 ` jb.1234abcd at gmail dot com 2013-04-30 22:58 ` [Bug c++/57111] Generalize -Wfree-nonheap-object to delete glisse at gcc dot gnu.org 2013-04-30 23:01 ` redi at gcc dot gnu.org 2020-11-05 17:52 ` msebor at gcc dot gnu.org 2020-11-09 14:51 ` redi at gcc dot gnu.org 2020-12-03 22:56 ` msebor at gcc dot gnu.org 2020-12-08 20:51 ` msebor at gcc dot gnu.org [this message] 2020-12-14 20:31 ` cvs-commit at gcc dot gnu.org 2020-12-14 20:34 ` msebor at gcc dot gnu.org 2021-01-10 23:21 ` cvs-commit at gcc dot gnu.org 2023-06-14 9:43 ` cvs-commit at gcc dot gnu.org 2023-06-15 7:21 ` cvs-commit 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-57111-4-1PeNAv242O@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).