From: David Malcolm <dmalcolm@redhat.com>
To: priour.be@gmail.com, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] analyzer: Fix regression bug after r14-1632-g9589a46ddadc8b [PR110198]
Date: Thu, 29 Jun 2023 16:29:02 -0400 [thread overview]
Message-ID: <d3e7caa1ce22e5cb4dde04429e4349b561b4eb9a.camel@redhat.com> (raw)
In-Reply-To: <20230629184510.750143-1-vultkayn@gcc.gnu.org>
On Thu, 2023-06-29 at 20:45 +0200, priour.be@gmail.com wrote:
> From: benjamin priour <priour.be@gmail.com>
>
> See below formatting updates on my patch.
> In mail
> https://gcc.gnu.org/pipermail/gcc-patches/2023-June/623140.html,
> David Malcolm says regtesting failed for him.
>
> So I did it once more this morning rebased on fresh trunk dc93a0f633b
> and target x86_64-linux-gnu, the output was similar to last time:
>
> # from gcc_sources_testing
> gcc/contrib/compare_tests ../gcc_sources_control/build build
>
> # Comparing directories
> ## Dir1=../gcc_sources_control/build: 8 sum files
> ## Dir2=build: 8 sum files
>
> # Comparing 8 common sum files
> ## /bin/sh gcc/contrib/compare_tests /tmp/gxx-sum1.750468
> /tmp/gxx-sum2.750468
> Tests that now work, but didn't before (3 tests):
>
> g++.dg/analyzer/pr100244.C -std=c++14 (test for warnings, line
> 17)
> g++.dg/analyzer/pr100244.C -std=c++17 (test for warnings, line
> 17)
> g++.dg/analyzer/pr100244.C -std=c++20 (test for warnings, line
> 17)
>
> # No differences found in 8 common sum files
>
> Can you confirm formatting of the patch below, and perhaps regtest it
> ?
Looks good to me; you can go ahead and push this to trunk.
Thanks
Dave
next prev parent reply other threads:[~2023-06-29 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 18:45 priour.be
2023-06-29 20:29 ` David Malcolm [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-22 19:55 [PATCH] analyzer: Fix regression bug after r14-1632-g9589a46ddadc8b [pr110198] priour.be
2023-06-28 23:36 ` David Malcolm
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=d3e7caa1ce22e5cb4dde04429e4349b561b4eb9a.camel@redhat.com \
--to=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=priour.be@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).