From: David Malcolm <dmalcolm@redhat.com>
To: Ankur Saini <arsenic.secondary@gmail.com>,
gcc Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] analyzer: Impose recursion limit on indirect calls.
Date: Wed, 25 Aug 2021 09:22:04 -0400 [thread overview]
Message-ID: <5df6e7001a5792e5aeaf03de4658cad2c4bdc6e3.camel@redhat.com> (raw)
In-Reply-To: <02524C4A-6B71-44BD-90E3-E9328DCE32E7@gmail.com>
On Wed, 2021-08-25 at 13:39 +0530, Ankur Saini wrote:
> This should also fix the failing regression found in PR
> analyzer/101980.
>
> - The patch is in sync with current master
> - successfully bootstrapped and tested on x86_64-linux-gnu.
>
The patch is OK for trunk.
Thanks for fixing this
Dave
next prev parent reply other threads:[~2021-08-25 13:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 8:09 Ankur Saini
2021-08-25 13:22 ` David Malcolm [this message]
2021-08-25 13:54 ` Martin Liška
[not found] ` <9C51062C-3457-4345-9BDC-20F7FE4BFA1E@gmail.com>
2021-08-25 15:05 ` David Malcolm
2021-08-25 15:55 ` Ankur Saini
2021-08-25 17:15 ` David Malcolm
2021-08-27 12:44 ` Ankur Saini
2021-08-27 12:58 ` Martin Liška
2021-09-20 12:36 ` Ankur Saini
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=5df6e7001a5792e5aeaf03de4658cad2c4bdc6e3.camel@redhat.com \
--to=dmalcolm@redhat.com \
--cc=arsenic.secondary@gmail.com \
--cc=gcc-patches@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: 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).