On Thu, 2021-06-24 at 22:26 -0700, sunil.k.pandey via Gcc-patches
wrote:
> On Linux/x86_64,
>
> e9e2bad7251477db92ab9ebcdc010f9282dd9890 is the first bad commit
> commit e9e2bad7251477db92ab9ebcdc010f9282dd9890
> Author: Martin Sebor <mse...@redhat.com>
> Date: Thu Jun 24 19:22:06 2021 -0600
>
> middle-end: add support for per-location warning groups.
>
> caused
>
> FAIL: gcc.dg/analyzer/setjmp-2.c (test for excess errors)
>
> with GCC configured with
>
> ../../gcc/configure --prefix=/local/skpandey/gccwork/toolwork/gcc-
> bisect-master/master/r12-1805/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/setjmp-2.c --
> target_board='unix{-m32}'"
> $ cd {build_dir}/gcc && make check
> RUNTESTFLAGS="analyzer.exp=gcc.dg/analyzer/setjmp-2.c --
> target_board='unix{-m32\ -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check
> RUNTESTFLAGS="analyzer.exp=gcc.dg/analyzer/setjmp-2.c --
> target_board='unix{-m64}'"
> $ cd {build_dir}/gcc && make check
> RUNTESTFLAGS="analyzer.exp=gcc.dg/analyzer/setjmp-2.c --
> target_board='unix{-m64\ -march=cascadelake}'"
Thanks.
> (Please do not reply to this email, for question about this report,
> contact me at skpgkp2 at gmail dot com)
[dropping you from the reply]
I can reproduce this; it seems to be a bug in Martin's changes to
calls.c, rather than being specific to the analyzer.
I've filed it as:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101217
Dave
