public inbox for gcc-regression@sourceware.org
help / color / mirror / Atom feed
* [r13-1786 Regression] FAIL: gcc.dg/analyzer/stdarg-3.c (test for excess errors) on Linux/x86_64
@ 2022-07-22  1:35 skpandey
  2022-07-22 15:06 ` David Malcolm
  0 siblings, 1 reply; 2+ messages in thread
From: skpandey @ 2022-07-22  1:35 UTC (permalink / raw)
  To: gcc-patches, gcc-regression, dmalcolm

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)

with GCC configured with

../../gcc/configure --prefix=/local/skpandey/gccwork/toolwork/gcc-bisect-master/master/r13-1786/usr --enable-clocale=gnu --with-system-zlib --with-demangler-in-ld --with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet --without-isl --enable-libmpx x86_64-linux --disable-bootstrap

To reproduce:

$ cd {build_dir}/gcc && make check RUNTESTFLAGS="analyzer.exp=gcc.dg/analyzer/stdarg-3.c --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="analyzer.exp=gcc.dg/analyzer/stdarg-3.c --target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="analyzer.exp=gcc.dg/analyzer/stdarg-3.c --target_board='unix{-m64}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="analyzer.exp=gcc.dg/analyzer/stdarg-3.c --target_board='unix{-m64\ -march=cascadelake}'"

(Please do not reply to this email, for question about this report, contact me at skpgkp2 at gmail dot com)


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [r13-1786 Regression] FAIL: gcc.dg/analyzer/stdarg-3.c (test for excess errors) on Linux/x86_64
  2022-07-22  1:35 [r13-1786 Regression] FAIL: gcc.dg/analyzer/stdarg-3.c (test for excess errors) on Linux/x86_64 skpandey
@ 2022-07-22 15:06 ` David Malcolm
  0 siblings, 0 replies; 2+ messages in thread
From: David Malcolm @ 2022-07-22 15:06 UTC (permalink / raw)
  To: skpandey, gcc-patches, gcc-regression

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



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2022-07-22 15:06 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-07-22  1:35 [r13-1786 Regression] FAIL: gcc.dg/analyzer/stdarg-3.c (test for excess errors) on Linux/x86_64 skpandey
2022-07-22 15:06 ` David Malcolm

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).