public inbox for gcc-regression@sourceware.org
help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: skpandey@sc.intel.com, gcc-patches@gcc.gnu.org,
gcc-regression@gcc.gnu.org
Subject: Re: [r13-1786 Regression] FAIL: gcc.dg/analyzer/stdarg-3.c (test for excess errors) on Linux/x86_64
Date: Fri, 22 Jul 2022 11:06:11 -0400 [thread overview]
Message-ID: <4bf9bd3e5badd5bf0b5625c48e5ff16f1b8aa594.camel@redhat.com> (raw)
In-Reply-To: <20220722013555.452E6286470F@gskx-2.sc.intel.com>
On Thu, 2022-07-21 at 18:35 -0700, skpandey@sc.intel.com wrote:
> On Linux/x86_64,
>
> b852aa7f265424c8e2036899da5d8306ff06a16c is the first bad commit
> commit b852aa7f265424c8e2036899da5d8306ff06a16c
> Author: David Malcolm <dmalcolm@redhat.com>
> Date: Thu Jul 21 17:29:26 2022 -0400
>
> analyzer: fix -Wanalyzer-va-list-exhausted false +ve on va_arg in
> subroutine [PR106383]
>
> caused
>
> FAIL: gcc.dg/analyzer/stdarg-3.c (test for excess errors)
Thanks; I somehow managed to miss the FAIL when reviewing the test
results; sorry everyone; it points to a real issue in -fanalyzer for
va_arg in loops.
I've filed this as PR analyzer/106413 ("State explosion on va_arg when
va_start is in top-level function of analysis").
Dave
prev parent reply other threads:[~2022-07-22 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 1:35 skpandey
2022-07-22 15:06 ` 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=4bf9bd3e5badd5bf0b5625c48e5ff16f1b8aa594.camel@redhat.com \
--to=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc-regression@gcc.gnu.org \
--cc=skpandey@sc.intel.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).