From: Mike Stump <mikestump@comcast.net>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org,
Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>,
Martin Sebor <msebor@gmail.com>
Subject: Re: Remove 'gcc/testsuite/g++.dg/warn/Wfree-nonheap-object.s' (was: [PATCH] add -Wmismatched-new-delete to middle end (PR 90629))
Date: Wed, 7 Jun 2023 10:10:41 -0700 [thread overview]
Message-ID: <9F9F1210-7C63-441C-9DB8-50FDDDDF8DDB@comcast.net> (raw)
In-Reply-To: <87zg5b727b.fsf@euler.schwinge.homeip.net>
On Jun 7, 2023, at 7:54 AM, Thomas Schwinge <thomas@codesourcery.com> wrote:
>
> On 2020-11-03T16:56:48-0700, Martin Sebor via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>> Attached is a simple middle end implementation of detection of
>> mismatched pairs of calls to C++ new and delete, along with
>> a substantially enhanced implementation of -Wfree-nonheap-object.
>
> This eventually became commit dce6c58db87ebf7f4477bd3126228e73e4eeee97
> "Add support for detecting mismatched allocation/deallocation calls".
> Already in this original patch submission:
>
>> diff --git a/gcc/testsuite/g++.dg/warn/Wfree-nonheap-object.s b/gcc/testsuite/g++.dg/warn/Wfree-nonheap-object.s
>> new file mode 100644
>> index 00000000000..e69de29bb2d
>
> OK to push the attached
> "Remove 'gcc/testsuite/g++.dg/warn/Wfree-nonheap-object.s'"?
Ok.
prev parent reply other threads:[~2023-06-07 17:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 23:56 [PATCH] add -Wmismatched-new-delete to middle end (PR 90629) Martin Sebor
2020-11-17 0:54 ` Jeff Law
2020-11-17 18:02 ` Martin Sebor
2020-12-02 0:09 ` Jeff Law
2020-12-06 9:26 ` Martin Liška
2023-06-07 14:54 ` Remove 'gcc/testsuite/g++.dg/warn/Wfree-nonheap-object.s' (was: [PATCH] add -Wmismatched-new-delete to middle end (PR 90629)) Thomas Schwinge
2023-06-07 17:10 ` Mike Stump [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=9F9F1210-7C63-441C-9DB8-50FDDDDF8DDB@comcast.net \
--to=mikestump@comcast.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=msebor@gmail.com \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
--cc=thomas@codesourcery.com \
/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: link
Be 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).