Regressions on releases/gcc-13 at commit r13-8999 vs commit r13-8987 on Linux/i686
Regressions on releases/gcc-13 at commit r13-8999 vs commit r13-8987 on Linux/i686 New failures: New passes: FAIL: gcc.target/i386/pieces-memcpy-10.c scan-assembler-times vmovdqu[ \\t]+[^\n]*%xmm 4 FAIL: gcc.target/i386/pieces-memset-38.c scan-assembler-times vmovdqu[ \\t]+[^\n]*%xmm 2 FAIL: gcc.target/i386/pieces-memset-38.c scan-assembler-times vpcmpeqd[ \\t]+[^\n]*%xmm 1 FAIL: gcc.target/i386/pieces-memset-40.c scan-assembler-not %[re]bp FAIL: gcc.target/i386/pieces-memset-40.c scan-assembler-times vmovdqu[ \\t]+[^\n]*%xmm 4 FAIL: gcc.target/i386/pieces-memset-40.c scan-assembler-times vpbroadcastb[ \\t]+[^\n]*%xmm 1 FAIL: gcc.target/i386/pieces-memset-41.c scan-assembler-not %[re]bp FAIL: gcc.target/i386/pieces-memset-42.c scan-assembler-times vmovdqu[ \\t]+[^\n]*%xmm 2 FAIL: gcc.target/i386/pieces-memset-43.c scan-assembler-times vmovdqu[ \\t]+[^\n]*%xmm 2 FAIL: gcc.target/i386/pieces-memset-43.c scan-assembler-times vpcmpeqd[ \\t]+[^\n]*%xmm 1
Regressions on master at commit r15-3363 vs commit r15-3360 on Linux/x86_64
Regressions on master at commit r15-3363 vs commit r15-3360 on Linux/x86_64 New failures: New passes: FAIL: gcc.dg/vect/slp-54.c -flto -ffat-lto-objects scan-tree-dump vect "vectorizing stmts using SLP" FAIL: gcc.dg/vect/slp-54.c scan-tree-dump vect "vectorizing stmts using SLP"
Regressions on native/releases/gcc-13 at commit r13-8999 vs commit r13-8987 on Linux/x86_64
Regressions on releases/gcc-13 at commit r13-8999 vs commit r13-8987 on Linux/x86_64 New failures: FAIL: gcc.dg/vect/tsvc/vect-tsvc-s317.c execution test FAIL: gcc.dg/vect/tsvc/vect-tsvc-s317.c -flto -ffat-lto-objects execution test FAIL: libgomp.c++/../libgomp.c-c++-common/for-11.c execution test FAIL: libgomp.c++/../libgomp.c-c++-common/for-12.c execution test FAIL: libgomp.c++/../libgomp.c-c++-common/for-14.c execution test FAIL: libgomp.c++/../libgomp.c-c++-common/for-15.c execution test FAIL: libgomp.c++/../libgomp.c-c++-common/for-3.c execution test FAIL: libgomp.c++/../libgomp.c-c++-common/for-5.c execution test FAIL: libgomp.c++/../libgomp.c-c++-common/for-6.c execution test FAIL: libgomp.c/../libgomp.c-c++-common/for-6.c execution test FAIL: libgomp.c++/../libgomp.c-c++-common/for-9.c execution test New passes: FAIL: gcc.target/i386/pieces-memcpy-10.c scan-assembler-times vmovdqu[ \\t]+[^\n]*%xmm 4 FAIL: gcc.target/i386/pieces-memcpy-10.c scan-assembler-times vmovdqu[ \\t]+[^\n]*%xmm 4 FAIL: gcc.target/i386/pieces-memcpy-6.c scan-assembler-times vmovdqu[ \\t]+[^\n]*%xmm 4 FAIL: gcc.target/i386/pieces-memset-38.c scan-assembler-times vmovdqu[ \\t]+[^\n]*%xmm 2 FAIL: gcc.target/i386/pieces-memset-38.c scan-assembler-times vmovdqu[ \\t]+[^\n]*%xmm 2 FAIL: gcc.target/i386/pieces-memset-38.c scan-assembler-times vpcmpeqd[ \\t]+[^\n]*%xmm 1 FAIL: gcc.target/i386/pieces-memset-38.c scan-assembler-times vpcmpeqd[ \\t]+[^\n]*%xmm 1 FAIL: gcc.target/i386/pieces-memset-40.c scan-assembler-not %[re]bp FAIL: gcc.target/i386/pieces-memset-40.c scan-assembler-times vmovdqu[ \\t]+[^\n]*%xmm 4 FAIL: gcc.target/i386/pieces-memset-40.c scan-assembler-times vmovdqu[ \\t]+[^\n]*%xmm 4 FAIL: gcc.target/i386/pieces-memset-40.c scan-assembler-times vpbroadcastb[ \\t]+[^\n]*%xmm 1 FAIL: gcc.target/i386/pieces-memset-41.c scan-assembler-not %[re]bp FAIL: gcc.target/i386/pieces-memset-42.c scan-assembler-times vmovdqu[ \\t]+[^\n]*%xmm 2 FAIL: gcc.target/i386/pieces-memset-42.c scan-assembler-times vmovdqu[ \\t]+[^\n]*%xmm 2 FAIL: gcc.target/i386/pieces-memset-43.c scan-assembler-times vmovdqu[ \\t]+[^\n]*%xmm 2 FAIL: gcc.target/i386/pieces-memset-43.c scan-assembler-times vmovdqu[ \\t]+[^\n]*%xmm 2 FAIL: gcc.target/i386/pieces-memset-43.c scan-assembler-times vpcmpeqd[ \\t]+[^\n]*%xmm 1 FAIL: gcc.target/i386/pieces-memset-43.c scan-assembler-times vpcmpeqd[ \\t]+[^\n]*%xmm 1 FAIL: gcc.target/i386/pieces-strcpy-2.c scan-assembler-times vmovdqa[ \\t]+[^\n]*%xmm 4 FAIL: gcc.target/i386/pieces-strcpy-2.c scan-assembler-times vmovdqu[ \\t]+[^\n]*%xmm 4 FAIL: libgomp.c/../libgomp.c-c++-common/for-11.c execution test FAIL: libgomp.c/../libgomp.c-c++-common/for-12.c execution test FAIL: libgomp.c/../libgomp.c-c++-common/for-14.c execution test FAIL: libgomp.c/../libgomp.c-c++-common/for-15.c execution test FAIL: libgomp.c/../libgomp.c-c++-common/for-3.c execution test FAIL: libgomp.c/../libgomp.c-c++-common/for-9.c execution test
Regressions on master at commit r15-3363 vs commit r15-3360 on Linux/i686
Regressions on master at commit r15-3363 vs commit r15-3360 on Linux/i686 New failures: New passes: FAIL: gcc.dg/vect/slp-54.c -flto -ffat-lto-objects scan-tree-dump vect "vectorizing stmts using SLP" FAIL: gcc.dg/vect/slp-54.c scan-tree-dump vect "vectorizing stmts using SLP"
Regressions on native/releases/gcc-14 at commit r14-10625 vs commit r14-10621 on Linux/x86_64
Regressions on releases/gcc-14 at commit r14-10625 vs commit r14-10621 on Linux/x86_64 New failures: FAIL: libgomp.c/examples-4/teams-4.c execution test FAIL: libgomp.c++/../libgomp.c-c++-common/for-11.c execution test FAIL: libgomp.c/../libgomp.c-c++-common/for-11.c execution test FAIL: libgomp.c++/../libgomp.c-c++-common/for-14.c execution test FAIL: libgomp.c/../libgomp.c-c++-common/for-14.c execution test FAIL: libgomp.c++/../libgomp.c-c++-common/for-15.c execution test FAIL: libgomp.c/../libgomp.c-c++-common/for-15.c execution test FAIL: libgomp.c/../libgomp.c-c++-common/for-3.c execution test FAIL: libgomp.c++/../libgomp.c-c++-common/for-5.c execution test FAIL: libgomp.c/../libgomp.c-c++-common/for-5.c execution test FAIL: libgomp.c/../libgomp.c-c++-common/for-6.c execution test FAIL: libgomp.c++/../libgomp.c-c++-common/for-9.c execution test FAIL: libgomp.c/../libgomp.c-c++-common/for-9.c execution test New passes:
Regressions on native/master at commit r15-3379 vs commit r15-3361 on Linux/x86_64
Regressions on master at commit r15-3379 vs commit r15-3361 on Linux/x86_64 New failures: FAIL: gcc.dg/vect/slp-11a.c -flto -ffat-lto-objects scan-tree-dump-times vect "vectorizing stmts using SLP" 1 FAIL: gcc.dg/vect/slp-11a.c -flto -ffat-lto-objects scan-tree-dump-times vect "vectorizing stmts using SLP" 1 FAIL: gcc.dg/vect/slp-11a.c scan-tree-dump-times vect "vectorizing stmts using SLP" 1 FAIL: gcc.dg/vect/slp-11a.c scan-tree-dump-times vect "vectorizing stmts using SLP" 1 FAIL: gcc.dg/vect/slp-12a.c -flto -ffat-lto-objects scan-tree-dump-times vect "vectorizing stmts using SLP" 1 FAIL: gcc.dg/vect/slp-12a.c -flto -ffat-lto-objects scan-tree-dump-times vect "vectorizing stmts using SLP" 1 FAIL: gcc.dg/vect/slp-12a.c scan-tree-dump-times vect "vectorizing stmts using SLP" 1 FAIL: gcc.dg/vect/slp-12a.c scan-tree-dump-times vect "vectorizing stmts using SLP" 1 New passes: FAIL: gcc.dg/vect/slp-54.c -flto -ffat-lto-objects scan-tree-dump vect "vectorizing stmts using SLP" FAIL: gcc.dg/vect/slp-54.c scan-tree-dump vect "vectorizing stmts using SLP"
[r15-3352 Regression] FAIL: gcc.target/i386/vnniint8-auto-vectorize-3.c (test for excess errors) on Linux/x86_64
On Linux/x86_64,
b1f9fbb6da1a3ced57c3668cecc9f9449e1b237e is the first bad commit
commit b1f9fbb6da1a3ced57c3668cecc9f9449e1b237e
Author: Haochen Jiang
Date: Mon Sep 2 10:24:29 2024 +0800
i386: Auto vectorize sdot_prod, usdot_prod, udot_prod with AVX10.2
instructions
caused
FAIL: gcc.target/i386/vnniint16-auto-vectorize-3.c (test for excess errors)
FAIL: gcc.target/i386/vnniint8-auto-vectorize-3.c (test for excess errors)
with GCC configured with
../../gcc/configure
--prefix=/export/users/haochenj/src/gcc-bisect/master/master/r15-3352/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="i386.exp=gcc.target/i386/vnniint16-auto-vectorize-3.c
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check
RUNTESTFLAGS="i386.exp=gcc.target/i386/vnniint16-auto-vectorize-3.c
--target_board='unix{-m64\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check
RUNTESTFLAGS="i386.exp=gcc.target/i386/vnniint8-auto-vectorize-3.c
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check
RUNTESTFLAGS="i386.exp=gcc.target/i386/vnniint8-auto-vectorize-3.c
--target_board='unix{-m64\ -march=cascadelake}'"
(Please do not reply to this email, for question about this report, contact me
at haochen dot jiang at intel.com.)
(If you met problems with cascadelake related, disabling AVX512F in command
line might save that.)
(However, please make sure that there is no potential problems with AVX512.)
[r15-3356 Regression] FAIL: gcc.target/i386/avx10_2-bf-vector-fma-1.c (test for excess errors) on Linux/x86_64
On Linux/x86_64,
6d294fb8ac9baf2624446deaa4c995b7a7719823 is the first bad commit
commit 6d294fb8ac9baf2624446deaa4c995b7a7719823
Author: Levy Hsu
Date: Mon Sep 2 10:24:46 2024 +0800
i386: Support vectorized BF16 FMA with AVX10.2 instructions
caused
FAIL: gcc.target/i386/avx10_2-bf-vector-fma-1.c (test for excess errors)
with GCC configured with
../../gcc/configure
--prefix=/export/users/haochenj/src/gcc-bisect/master/master/r15-3356/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="i386.exp=gcc.target/i386/avx10_2-bf-vector-fma-1.c
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check
RUNTESTFLAGS="i386.exp=gcc.target/i386/avx10_2-bf-vector-fma-1.c
--target_board='unix{-m64\ -march=cascadelake}'"
(Please do not reply to this email, for question about this report, contact me
at haochen dot jiang at intel.com.)
(If you met problems with cascadelake related, disabling AVX512F in command
line might save that.)
(However, please make sure that there is no potential problems with AVX512.)
[r15-3354 Regression] FAIL: gcc.target/i386/avx10_2-compare-1b.c (test for excess errors) on Linux/x86_64
On Linux/x86_64,
3b1decef83003db9cf8667977c293435c0f3d024 is the first bad commit
commit 3b1decef83003db9cf8667977c293435c0f3d024
Author: Hu, Lin1
Date: Mon Sep 2 10:24:36 2024 +0800
i386: Optimize generate insn for AVX10.2 compare
caused
FAIL: gcc.target/i386/avx10_2-compare-1b.c (test for excess errors)
with GCC configured with
../../gcc/configure
--prefix=/export/users/haochenj/src/gcc-bisect/master/master/r15-3354/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="i386.exp=gcc.target/i386/avx10_2-compare-1b.c
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check
RUNTESTFLAGS="i386.exp=gcc.target/i386/avx10_2-compare-1b.c
--target_board='unix{-m64\ -march=cascadelake}'"
(Please do not reply to this email, for question about this report, contact me
at haochen dot jiang at intel.com.)
(If you met problems with cascadelake related, disabling AVX512F in command
line might save that.)
(However, please make sure that there is no potential problems with AVX512.)
[r15-3357 Regression] FAIL: gcc.target/i386/avx10_2-bf-vector-smaxmin-1.c (test for excess errors) on Linux/x86_64
On Linux/x86_64,
29ef601973d7b79338694e59581d4c24bcd07f69 is the first bad commit
commit 29ef601973d7b79338694e59581d4c24bcd07f69
Author: Levy Hsu
Date: Mon Sep 2 10:24:47 2024 +0800
i386: Support vectorized BF16 smaxmin with AVX10.2 instructions
caused
FAIL: gcc.target/i386/avx10_2-bf-vector-smaxmin-1.c (test for excess errors)
with GCC configured with
../../gcc/configure
--prefix=/export/users/haochenj/src/gcc-bisect/master/master/r15-3357/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="i386.exp=gcc.target/i386/avx10_2-bf-vector-smaxmin-1.c
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check
RUNTESTFLAGS="i386.exp=gcc.target/i386/avx10_2-bf-vector-smaxmin-1.c
--target_board='unix{-m64\ -march=cascadelake}'"
(Please do not reply to this email, for question about this report, contact me
at haochen dot jiang at intel.com.)
(If you met problems with cascadelake related, disabling AVX512F in command
line might save that.)
(However, please make sure that there is no potential problems with AVX512.)
[r15-3355 Regression] FAIL: gcc.target/i386/avx10_2-bf-vector-operations-1.c (test for excess errors) on Linux/x86_64
On Linux/x86_64,
f82fa0da4d9e1fdaf5e4edd70364d5781534ce11 is the first bad commit
commit f82fa0da4d9e1fdaf5e4edd70364d5781534ce11
Author: Levy Hsu
Date: Mon Sep 2 10:24:45 2024 +0800
i386: Support vectorized BF16 add/sub/mul/div with AVX10.2 instructions
caused
FAIL: gcc.target/i386/avx10_2-bf-vector-operations-1.c (test for excess errors)
with GCC configured with
../../gcc/configure
--prefix=/export/users/haochenj/src/gcc-bisect/master/master/r15-3355/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="i386.exp=gcc.target/i386/avx10_2-bf-vector-operations-1.c
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check
RUNTESTFLAGS="i386.exp=gcc.target/i386/avx10_2-bf-vector-operations-1.c
--target_board='unix{-m64\ -march=cascadelake}'"
(Please do not reply to this email, for question about this report, contact me
at haochen dot jiang at intel.com.)
(If you met problems with cascadelake related, disabling AVX512F in command
line might save that.)
(However, please make sure that there is no potential problems with AVX512.)
[r15-3359 Regression] FAIL: gcc.target/i386/avx10_2-bf-vector-cmpp-1.c (test for excess errors) on Linux/x86_64
On Linux/x86_64,
f77435aa3911c437cba71991509eee57b333b3ce is the first bad commit
commit f77435aa3911c437cba71991509eee57b333b3ce
Author: Levy Hsu
Date: Mon Sep 2 10:24:49 2024 +0800
i386: Support vec_cmp for V8BF/V16BF/V32BF in AVX10.2
caused
FAIL: gcc.target/i386/avx10_2-bf-vector-cmpp-1.c (test for excess errors)
with GCC configured with
../../gcc/configure
--prefix=/export/users/haochenj/src/gcc-bisect/master/master/r15-3359/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="i386.exp=gcc.target/i386/avx10_2-bf-vector-cmpp-1.c
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check
RUNTESTFLAGS="i386.exp=gcc.target/i386/avx10_2-bf-vector-cmpp-1.c
--target_board='unix{-m64\ -march=cascadelake}'"
(Please do not reply to this email, for question about this report, contact me
at haochen dot jiang at intel.com.)
(If you met problems with cascadelake related, disabling AVX512F in command
line might save that.)
(However, please make sure that there is no potential problems with AVX512.)
Regressions on master at commit r15-3383 vs commit r15-3380 on Linux/x86_64
Regressions on master at commit r15-3383 vs commit r15-3380 on Linux/x86_64 New failures: FAIL: gcc.dg/torture/convert-dfp-2.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects (test for excess errors) FAIL: gcc.dg/torture/convert-dfp.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects (test for excess errors) New passes:
[Linaro-TCWG-CI] gcc-15-3250-g7f4f1bb29a4: FAIL: 1 regressions on master-thumb_m55_hard_eabi
Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolch...@lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. We track this report status in https://linaro.atlassian.net/browse/GNU-1326 , please let us know if you are looking at the problem and/or when you have a fix. In arm-eabi cortex-m55 hard after: | commit gcc-15-3250-g7f4f1bb29a4 | Author: Jason Merrill | Date: Tue Aug 27 13:14:45 2024 -0400 | | c++: add missing -Wc++??-extensions checks | | The pedwarns for each of these features should be silenced by | the appropriate -Wno-c++??-extensions. | | The handle_pragma_diagnostic_impl change is necessary so that we handle | -Wc++23-extensions early so it's available to interpret_float while lexing. | ... 20 lines of the commit log omitted. FAIL: 1 regressions regressions.sum: === g++ tests === Running g++:g++.dg/dg.exp ... FAIL: g++.dg/cpp23/ext-floating19.C -std=c++26 (test for excess errors) You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m55_hard_eabi-build/577/artifact/artifacts/00-sumfiles/ The full lists of regressions and improvements as well as configure and make commands are in - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m55_hard_eabi-build/577/artifact/artifacts/notify/ The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m55_hard_eabi-build/577/artifact/artifacts/sumfiles/xfails.xfail The configuration of this build is: CI config tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv8.1-m.main+mve.fp+fp.dp -mtune=cortex-m55 -mfloat-abi=hard -mfpu=auto -8<--8<--8<-- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m55_hard_eabi-build/577/artifact/artifacts Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m55_hard_eabi-build/576/artifact/artifacts Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/7f4f1bb29a47fbe63a15dda8acfe247b2e934959/tcwg_gnu_embed_check_gcc/master-thumb_m55_hard_eabi/reproduction_instructions.txt Full commit : https://github.com/gcc-mirror/gcc/commit/7f4f1bb29a47fbe63a15dda8acfe247b2e934959 List of configurations that regressed due to this commit : * tcwg_gnu_embed_check_gcc ** master-thumb_m55_hard_eabi *** FAIL: 1 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/7f4f1bb29a47fbe63a15dda8acfe247b2e934959/tcwg_gnu_embed_check_gcc/master-thumb_m55_hard_eabi/details.txt *** https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m55_hard_eabi-build/577/artifact/artifacts
[r15-3362 Regression] FAIL: gcc.dg/vect/slp-12a.c scan-tree-dump-times vect "vectorizing stmts using SLP" 1 on Linux/x86_64
On Linux/x86_64,
464067a242150628ceb0d47daf2297f29a31743c is the first bad commit
commit 464067a242150628ceb0d47daf2297f29a31743c
Author: Richard Biener
Date: Mon May 13 14:57:01 2024 +0200
lower SLP load permutation to interleaving
caused
FAIL: gcc.dg/vect/slp-11a.c -flto -ffat-lto-objects scan-tree-dump-times vect
"vectorizing stmts using SLP" 1
FAIL: gcc.dg/vect/slp-11a.c scan-tree-dump-times vect "vectorizing stmts using
SLP" 1
FAIL: gcc.dg/vect/slp-12a.c -flto -ffat-lto-objects scan-tree-dump-times vect
"vectorizing stmts using SLP" 1
FAIL: gcc.dg/vect/slp-12a.c scan-tree-dump-times vect "vectorizing stmts using
SLP" 1
with GCC configured with
../../gcc/configure
--prefix=/export/users/haochenj/src/gcc-bisect/master/master/r15-3362/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="vect.exp=gcc.dg/vect/slp-11a.c
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="vect.exp=gcc.dg/vect/slp-11a.c
--target_board='unix{-m64\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="vect.exp=gcc.dg/vect/slp-12a.c
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="vect.exp=gcc.dg/vect/slp-12a.c
--target_board='unix{-m64\ -march=cascadelake}'"
(Please do not reply to this email, for question about this report, contact me
at haochen dot jiang at intel.com.)
(If you met problems with cascadelake related, disabling AVX512F in command
line might save that.)
(However, please make sure that there is no potential problems with AVX512.)
[Linaro-TCWG-CI] gcc-15-3363-g9aaedfc4146c: FAIL: 6 regressions: 8 improvements on aarch64
Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolch...@lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. We track this report status in https://linaro.atlassian.net/browse/GNU-1325 , please let us know if you are looking at the problem and/or when you have a fix. In gcc_check master-aarch64 after: | commit gcc-15-3363-g9aaedfc4146c | Author: Richard Biener | Date: Fri Jul 5 10:35:08 2024 +0200 | | load and store-lanes with SLP | | The following is a prototype for how to represent load/store-lanes | within SLP. I've for now settled with having a single load node | with multiple permute nodes acting as selection, one for each loaded lane | and a single store node fed from all stored lanes. For | | ... 171 lines of the commit log omitted. FAIL: 6 regressions: 8 improvements regressions.sum: === gcc tests === Running gcc:gcc.target/aarch64/aarch64.exp ... FAIL: gcc.target/aarch64/store_lane_spill_1.c scan-assembler-not \\tst1\\t Running gcc:gcc.target/aarch64/sve/aarch64-sve.exp ... FAIL: gcc.target/aarch64/sve/mask_struct_store_4.c scan-assembler-not \\tst2b\\t.z[0-9] FAIL: gcc.target/aarch64/sve/mask_struct_store_4.c scan-assembler-not \\tst2d\\t.z[0-9] FAIL: gcc.target/aarch64/sve/mask_struct_store_4.c scan-assembler-not \\tst2h\\t.z[0-9] FAIL: gcc.target/aarch64/sve/mask_struct_store_4.c scan-assembler-not \\tst2w\\t.z[0-9] ... and 2 more entries improvements.sum: === gcc tests === Running gcc:gcc.dg/vect/vect.exp ... FAIL: gcc.dg/vect/slp-51.c -flto -ffat-lto-objects scan-tree-dump vect "vectorizing stmts using SLP" FAIL: gcc.dg/vect/slp-51.c scan-tree-dump vect "vectorizing stmts using SLP" FAIL: gcc.dg/vect/slp-52.c scan-tree-dump vect "vectorizing stmts using SLP" FAIL: gcc.dg/vect/slp-52.c -flto -ffat-lto-objects scan-tree-dump vect "vectorizing stmts using SLP" FAIL: gcc.dg/vect/slp-cond-2-big-array.c -flto -ffat-lto-objects scan-tree-dump-times vect "vectorizing stmts using SLP" 4 FAIL: gcc.dg/vect/slp-cond-2-big-array.c scan-tree-dump-times vect "vectorizing stmts using SLP" 4 FAIL: gcc.dg/vect/slp-cond-2.c scan-tree-dump-times vect "vectorizing stmts using SLP" 4 ... and 2 more entries You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2545/artifact/artifacts/00-sumfiles/ The full lists of regressions and improvements as well as configure and make commands are in - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2545/artifact/artifacts/notify/ The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2545/artifact/artifacts/sumfiles/xfails.xfail The configuration of this build is: CI config tcwg_gcc_check master-aarch64 -8<--8<--8<-- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2545/artifact/artifacts Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2544/artifact/artifacts Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/9aaedfc4146c5e4b8412913a6ca4092a2731c35c/tcwg_gcc_check/master-aarch64/reproduction_instructions.txt Full commit : https://github.com/gcc-mirror/gcc/commit/9aaedfc4146c5e4b8412913a6ca4092a2731c35c List of configurations that regressed due to this commit : * tcwg_gcc_check ** master-aarch64 *** FAIL: 6 regressions: 8 improvements *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/9aaedfc4146c5e4b8412913a6ca4092a2731c35c/tcwg_gcc_check/master-aarch64/details.txt *** https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2545/artifact/artifacts
RE: [r15-3359 Regression] FAIL: gcc.target/i386/avx10_2-bf-vector-cmpp-1.c (test for excess errors) on Linux/x86_64
As each AVX10.2 testcases previously, this is caused by option combination
warning,
which is expected.
> From: haochen.jiang
> Sent: Monday, September 2, 2024 9:06 PM
>
> On Linux/x86_64,
>
> f77435aa3911c437cba71991509eee57b333b3ce is the first bad commit commit
> f77435aa3911c437cba71991509eee57b333b3ce
> Author: Levy Hsu
> Date: Mon Sep 2 10:24:49 2024 +0800
>
> i386: Support vec_cmp for V8BF/V16BF/V32BF in AVX10.2
>
> caused
>
> FAIL: gcc.target/i386/avx10_2-bf-vector-cmpp-1.c (test for excess errors)
>
> with GCC configured with
>
> ../../gcc/configure --prefix=/export/users/haochenj/src/gcc-
> bisect/master/master/r15-3359/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="i386.exp=gcc.target/i386/avx10_2-bf-vector-cmpp-1.c --
> target_board='unix{-m32\ -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check
> RUNTESTFLAGS="i386.exp=gcc.target/i386/avx10_2-bf-vector-cmpp-1.c --
> target_board='unix{-m64\ -march=cascadelake}'"
>
> (Please do not reply to this email, for question about this report, contact
> me at
> haochen dot jiang at intel.com.) (If you met problems with cascadelake
> related,
> disabling AVX512F in command line might save that.) (However, please make sure
> that there is no potential problems with AVX512.)
Regressions on master at commit r15-3391 vs commit r15-3383 on Linux/x86_64
Regressions on master at commit r15-3391 vs commit r15-3383 on Linux/x86_64 New failures: New passes: FAIL: gcc.dg/torture/convert-dfp-2.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects (test for excess errors) FAIL: gcc.dg/torture/convert-dfp.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects (test for excess errors)
Regressions on native/master at commit r15-3391 vs commit r15-3386 on Linux/x86_64
Regressions on master at commit r15-3391 vs commit r15-3386 on Linux/x86_64 New failures: FAIL: gcc.target/i386/avx10_2-partial-bf-vector-fast-math-1.c (test for excess errors) FAIL: gcc.target/i386/avx10_2-partial-bf-vector-operations-1.c (test for excess errors) New passes:
Re: [r15-3359 Regression] FAIL: gcc.target/i386/avx10_2-bf-vector-cmpp-1.c (test for excess errors) on Linux/x86_64
On Tue, Sep 3, 2024 at 9:45 AM Jiang, Haochen via Gcc-regression wrote: > > As each AVX10.2 testcases previously, this is caused by option combination > warning, > which is expected. > Can we put the warning for mix usage of mavx10 and -mavx512f under -Wpsabi And add -Wno-psabi in addition to -march=cascadelake to avoid the false positive? -- BR, Hongtao
RE: [r15-3359 Regression] FAIL: gcc.target/i386/avx10_2-bf-vector-cmpp-1.c (test for excess errors) on Linux/x86_64
> -Original Message- > From: Hongtao Liu > Sent: Tuesday, September 3, 2024 1:47 PM > To: Jiang, Haochen > Cc: haochen.jiang ; ad...@levyhsu.com; gcc- > regress...@gcc.gnu.org; gcc-patc...@gcc.gnu.org > Subject: Re: [r15-3359 Regression] FAIL: gcc.target/i386/avx10_2-bf-vector- > cmpp-1.c (test for excess errors) on Linux/x86_64 > > On Tue, Sep 3, 2024 at 9:45 AM Jiang, Haochen via Gcc-regression > wrote: > > > > As each AVX10.2 testcases previously, this is caused by option combination > warning, > > which is expected. > > > Can we put the warning for mix usage of mavx10 and -mavx512f under - > Wpsabi > And add -Wno-psabi in addition to -march=cascadelake to avoid the > false positive? We could do that if nobody has objection to that. Thx, Haochen > > -- > BR, > Hongtao
Regressions on master at commit r15-3392 vs commit r15-3391 on Linux/x86_64
Regressions on master at commit r15-3392 vs commit r15-3391 on Linux/x86_64 New failures: FAIL: gcc.target/i386/avx10_2-512-bf-vector-smaxmin-1.c scan-assembler-times vmaxpbf16 1 FAIL: gcc.target/i386/avx10_2-512-bf-vector-smaxmin-1.c scan-assembler-times vmaxpbf16 1 FAIL: gcc.target/i386/avx10_2-512-bf-vector-smaxmin-1.c scan-assembler-times vminpbf16 1 FAIL: gcc.target/i386/avx10_2-512-bf-vector-smaxmin-1.c scan-assembler-times vminpbf16 1 FAIL: gcc.target/i386/avx10_2-bf-vector-smaxmin-1.c scan-assembler-times vmaxpbf16 2 FAIL: gcc.target/i386/avx10_2-bf-vector-smaxmin-1.c scan-assembler-times vmaxpbf16 2 FAIL: gcc.target/i386/avx10_2-bf-vector-smaxmin-1.c scan-assembler-times vminpbf16 2 FAIL: gcc.target/i386/avx10_2-bf-vector-smaxmin-1.c scan-assembler-times vminpbf16 2 New passes:
Regressions on master at commit r15-3392 vs commit r15-3391 on Linux/i686
Regressions on master at commit r15-3392 vs commit r15-3391 on Linux/i686 New failures: FAIL: gcc.target/i386/avx10_2-512-bf-vector-smaxmin-1.c scan-assembler-times vmaxpbf16 1 FAIL: gcc.target/i386/avx10_2-512-bf-vector-smaxmin-1.c scan-assembler-times vminpbf16 1 FAIL: gcc.target/i386/avx10_2-bf-vector-smaxmin-1.c scan-assembler-times vmaxpbf16 2 FAIL: gcc.target/i386/avx10_2-bf-vector-smaxmin-1.c scan-assembler-times vminpbf16 2 New passes:
Re: [r15-3359 Regression] FAIL: gcc.target/i386/avx10_2-bf-vector-cmpp-1.c (test for excess errors) on Linux/x86_64
On Tue, Sep 3, 2024 at 7:36 AM Jiang, Haochen wrote: > > > > > -Original Message- > > From: Hongtao Liu > > Sent: Tuesday, September 3, 2024 1:47 PM > > To: Jiang, Haochen > > Cc: haochen.jiang ; ad...@levyhsu.com; gcc- > > regress...@gcc.gnu.org; gcc-patc...@gcc.gnu.org > > Subject: Re: [r15-3359 Regression] FAIL: gcc.target/i386/avx10_2-bf-vector- > > cmpp-1.c (test for excess errors) on Linux/x86_64 > > > > On Tue, Sep 3, 2024 at 9:45 AM Jiang, Haochen via Gcc-regression > > wrote: > > > > > > As each AVX10.2 testcases previously, this is caused by option combination > > warning, > > > which is expected. > > > > > Can we put the warning for mix usage of mavx10 and -mavx512f under - > > Wpsabi > > And add -Wno-psabi in addition to -march=cascadelake to avoid the > > false positive? > > We could do that if nobody has objection to that. But mixing both doesn't do anything to the ABI so -Wpsabi sounds like the wrong bucket to me. Instead we have to solve the issue at hand - I would expect users to run into this warning as well if we do within our testsuite? Richard. > Thx, > Haochen > > > > > -- > > BR, > > Hongtao
