From: Diego Novillo <dnovillo@google.com>
To: Mark Heffernan <meheff@google.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR middle-end/38509: add -Wfree-nonheap-object warning option
Date: Mon, 22 Aug 2011 19:13:00 -0000 [thread overview]
Message-ID: <4E52A614.1040203@google.com> (raw)
In-Reply-To: <CAOi2v+SNg15yKDo22Q0QgDtMoxzkOa13ybZ9oZVTGzrp+5Z86g@mail.gmail.com>
On 11-08-21 18:14 , Mark Heffernan wrote:
> Ping?
>
> Mark
>
> On Fri, Aug 12, 2011 at 9:41 AM, Mark Heffernan<meheff@google.com> wrote:
>> This patch adds an option for enabling/disabling the warning for
>> attempting to free nonheap objects (PR/38509). The warning is
>> imprecise and can issue false positives.
>>
>> Bootstrapped on x86-64. Ok for trunk?
>>
>> Mark
>>
>> 2011-08-11 Mark Heffernan<meheff@google.com>
>>
>> PR middle-end/38509
>> * common.opt (Wfree-nonheap-object): New option.
>> * doc/invoke.texi (Warning options): Document -Wfree-nonheap-object.
>> * builtins.c (maybe_emit_free_warning): Add OPT_Wfree_nonheap_object
>> to warning.
OK.
Diego.
prev parent reply other threads:[~2011-08-22 18:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 17:27 Mark Heffernan
2011-08-22 7:23 ` Mark Heffernan
2011-08-22 19:13 ` Diego Novillo [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=4E52A614.1040203@google.com \
--to=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=meheff@google.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).