From: David Malcolm <dmalcolm@redhat.com>
To: Mir Immad <mirimnan017@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 1/2] analyzer: show close event for use_after_close diagnostic
Date: Tue, 05 Jul 2022 16:50:43 -0400 [thread overview]
Message-ID: <5888488873bd4d780786031a0aeae904e64fd54b.camel@redhat.com> (raw)
In-Reply-To: <CAE1-7owa7nexL8sBHerU_xTDPWC-Pab3MqUam81q3WVyF0rYLQ@mail.gmail.com>
On Tue, 2022-07-05 at 23:07 +0530, Mir Immad wrote:
[...snip...]
> gcc/analyzer/sm-fd.cc | 13 +++++++++++--
> gcc/testsuite/gcc.dg/analyzer/fd-4.c | 4 ++--
> 2 files changed, 13 insertions(+), 4 deletions(-)
>
> diff --git a/gcc/analyzer/sm-fd.cc b/gcc/analyzer/sm-fd.cc
> index 4058ac53308..a85c95cc502 100644
> --- a/gcc/analyzer/sm-fd.cc
> +++ b/gcc/analyzer/sm-fd.cc
> @@ -454,7 +454,10 @@ public:
> return label_text::borrow ("opened here");
>
> if (change.m_new_state == m_sm.m_closed)
> + {
> + m_first_close_event = change.m_event_id;
> return change.formatted_print ("closed here");
> + }
Looks like the indentation isn't quite right here, or did the patch get
mangled during the emailing process?
[...snip...]
Otherwise, the patch looks good.
Thanks
Dave
prev parent reply other threads:[~2022-07-05 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 17:37 Mir Immad
2022-07-05 20:50 ` David Malcolm [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=5888488873bd4d780786031a0aeae904e64fd54b.camel@redhat.com \
--to=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mirimnan017@gmail.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).