Regressions on master at commit r15-3886 vs commit r15-3883 on Linux/i686
Regressions on master at commit r15-3886 vs commit r15-3883 on Linux/i686 New failures: FAIL: gcc.target/i386/part-vect-popcount-1.c scan-assembler-times vpopcntb[^\n\r]*xmm[0-9] 4 FAIL: gcc.target/i386/part-vect-popcount-1.c scan-assembler-times vpopcntw[^\n\r]*xmm[0-9] 3 New passes:
[r15-3862 Regression] FAIL: gcc.dg/pr109393.c scan-tree-dump-times optimized "return 1;" 3 on Linux/x86_64
On Linux/x86_64,
08b8341f209be7c7e301853bdbbcad4f8e1695f5 is the first bad commit
commit 08b8341f209be7c7e301853bdbbcad4f8e1695f5
Author: Konstantinos Eleftheriou
Date: Thu Sep 5 15:59:59 2024 +0200
match: Change (A * B) + (-C) to (B - C/A) * A, if C multiple of A [PR109393]
caused
FAIL: gcc.dg/pr109393.c scan-tree-dump-times optimized "return 1;" 3
with GCC configured with
../../gcc/configure
--prefix=/export/users/haochenj/src/gcc-bisect/master/master/r15-3862/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="dg.exp=gcc.dg/pr109393.c
--target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/pr109393.c
--target_board='unix{-m32\ -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-3874 vs commit r15-3871 on Linux/x86_64
Regressions on master at commit r15-3874 vs commit r15-3871 on Linux/x86_64 New failures: New passes: FAIL: gfortran.dg/unsigned_25.f90 -O0 (test for excess errors) FAIL: gfortran.dg/unsigned_25.f90 -O1 (test for excess errors) FAIL: gfortran.dg/unsigned_25.f90 -O2 (test for excess errors) FAIL: gfortran.dg/unsigned_25.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess errors) FAIL: gfortran.dg/unsigned_25.f90 -O3 -g (test for excess errors) FAIL: gfortran.dg/unsigned_25.f90 -Os (test for excess errors)
[Linaro-TCWG-CI] gcc-15-3862-g08b8341f209b: FAIL: 1 regressions on arm
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 understand 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-1353 ,
please let us know if you are looking at the problem and/or when you have a fix.
In gcc_check master-arm after:
| commit gcc-15-3862-g08b8341f209b
| Author: Konstantinos Eleftheriou
| Date: Thu Sep 5 15:59:59 2024 +0200
|
| match: Change (A * B) + (-C) to (B - C/A) * A, if C multiple of A
[PR109393]
|
| The following function:
|
| int foo(int *a, int j)
| {
| int k = j - 1;
| ... 31 lines of the commit log omitted.
FAIL: 1 regressions
regressions.sum:
=== gcc tests ===
Running gcc:gcc.dg/dg.exp ...
FAIL: gcc.dg/pr109393.c scan-tree-dump-times optimized "return 1;" 3
You can find the failure logs in *.log.1.xz files in
-
https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2759/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-arm-build/2759/artifact/artifacts/notify/
The list of [ignored] baseline and flaky failures are in
-
https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2759/artifact/artifacts/sumfiles/xfails.xfail
The configuration of this build is:
CI config tcwg_gcc_check master-arm
-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-arm-build/2759/artifact/artifacts
Reference build :
https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2758/artifact/artifacts
Reproduce last good and first bad builds:
https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/08b8341f209be7c7e301853bdbbcad4f8e1695f5/tcwg_gcc_check/master-arm/reproduction_instructions.txt
Full commit :
https://github.com/gcc-mirror/gcc/commit/08b8341f209be7c7e301853bdbbcad4f8e1695f5
List of configurations that regressed due to this commit :
* tcwg_gcc_check
** master-arm
*** FAIL: 1 regressions
***
https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/08b8341f209be7c7e301853bdbbcad4f8e1695f5/tcwg_gcc_check/master-arm/details.txt
***
https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2759/artifact/artifacts
Regressions on native/master at commit r15-3872 vs commit r15-3869 on Linux/x86_64
Regressions on master at commit r15-3872 vs commit r15-3869 on Linux/x86_64 New failures: New passes: FAIL: gfortran.dg/unsigned_25.f90 -O0 (test for excess errors) FAIL: gfortran.dg/unsigned_25.f90 -O1 (test for excess errors) FAIL: gfortran.dg/unsigned_25.f90 -O2 (test for excess errors) FAIL: gfortran.dg/unsigned_25.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess errors) FAIL: gfortran.dg/unsigned_25.f90 -O3 -g (test for excess errors) FAIL: gfortran.dg/unsigned_25.f90 -Os (test for excess errors)
Regressions on master at commit r15-3874 vs commit r15-3871 on Linux/i686
Regressions on master at commit r15-3874 vs commit r15-3871 on Linux/i686 New failures: New passes: FAIL: 30_threads/future/members/poll.cc -std=gnu++17 execution test FAIL: gfortran.dg/unsigned_25.f90 -O0 (test for excess errors) FAIL: gfortran.dg/unsigned_25.f90 -O1 (test for excess errors) FAIL: gfortran.dg/unsigned_25.f90 -O2 (test for excess errors) FAIL: gfortran.dg/unsigned_25.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess errors) FAIL: gfortran.dg/unsigned_25.f90 -O3 -g (test for excess errors) FAIL: gfortran.dg/unsigned_25.f90 -Os (test for excess errors)
[Linaro-TCWG-CI] gcc-15-3859-g63a598deb0c9: FAIL: 3 regressions 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 understand 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-1352 , 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-3859-g63a598deb0c9 | Author: Jason Merrill | Date: Thu Sep 12 12:15:51 2024 -0400 | | libstdc++: #ifdef out #pragma GCC system_header | | In r15-3714-gd3a7302ec5985a I added -Wsystem-headers to the libstdc++ build | flags to help catch problems in the library. This patch takes a different | approach, of disabling the #pragma system_header unless _GLIBCXX_SYSHDR is | defined. As a result, the testsuites will treat them as non-system-headers | to get better warning coverage during regression testing of both gcc and | ... 375 lines of the commit log omitted. FAIL: 3 regressions regressions.sum: === libstdc++ tests === Running libstdc++:libstdc++-dg/conformance.exp ... FAIL: 17_intro/headers/c++2011/parallel_mode.cc (test for excess errors) FAIL: 17_intro/headers/c++2014/parallel_mode.cc (test for excess errors) FAIL: 17_intro/headers/c++2017/parallel_mode.cc -std=gnu++17 (test for excess errors) You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2657/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/2657/artifact/artifacts/notify/ The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2657/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/2657/artifact/artifacts Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2656/artifact/artifacts Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/63a598deb0c9fcb8704af6ef90f0b905942b0276/tcwg_gcc_check/master-aarch64/reproduction_instructions.txt Full commit : https://github.com/gcc-mirror/gcc/commit/63a598deb0c9fcb8704af6ef90f0b905942b0276 List of configurations that regressed due to this commit : * tcwg_gcc_check ** master-aarch64 *** FAIL: 3 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/63a598deb0c9fcb8704af6ef90f0b905942b0276/tcwg_gcc_check/master-aarch64/details.txt *** https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2657/artifact/artifacts
Regressions on master at commit r15-3854 vs commit r15-3848 on Linux/x86_64
Regressions on master at commit r15-3854 vs commit r15-3848 on Linux/x86_64 New failures: FAIL: gcc.dg/lto/save-temps c_lto_save-temps_0.o-c_lto_save-temps_0.o link, -O -flto -save-temps New passes:
Regressions on master at commit r15-3869 vs commit r15-3861 on Linux/x86_64
Regressions on master at commit r15-3869 vs commit r15-3861 on Linux/x86_64 New failures: FAIL: gcc.dg/pr109393.c scan-tree-dump-times optimized "return 1;" 3 New passes:
Regressions on native/master at commit r15-3869 vs commit r15-3857 on Linux/x86_64
Regressions on master at commit r15-3869 vs commit r15-3857 on Linux/x86_64 New failures: FAIL: gcc.dg/pr109393.c scan-tree-dump-times optimized "return 1;" 3 New passes:
Re: Regressions on native/master at commit r15-3869 vs commit r15-3857 on Linux/x86_64
I filed PR116845 for this.
Regressions on master at commit r15-3871 vs commit r15-3863 on Linux/i686
Regressions on master at commit r15-3871 vs commit r15-3863 on Linux/i686 New failures: FAIL: 30_threads/future/members/poll.cc -std=gnu++17 execution test New passes:
Re: [Linaro-TCWG-CI] gcc-15-3607-g9a94c8ffdc8b: FAIL: 23 regressions: 22 improvements on master-thumb_m23_soft_eabi
On 24/09/2024 22:20, Maxim Kuvyrkov wrote: On Sep 25, 2024, at 05:13, Richard Earnshaw (lists) wrote: On 21/09/2024 08:49, ci_not...@linaro.org wrote: 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 understand 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-1349 , please let us know if you are looking at the problem and/or when you have a fix. In arm-eabi cortex-m23 soft after: | commit gcc-15-3607-g9a94c8ffdc8b | Author: Richard Earnshaw | Date: Thu Sep 12 14:24:55 2024 +0100 | | arm: testsuite: make use of -mcpu=unset/-march=unset | | This patch makes use of the new ability to unset the CPU or | architecture flags on the command line to enable several more tests on | Arm. It doesn't cover every case and it does enable some tests that | now fail for different reasons when the tests are no-longer skipped; | these were failing anyway for other testsuite configurations, so it's | ... 22 lines of the commit log omitted. FAIL: 23 regressions: 22 improvements regressions.sum: === gcc tests === Running gcc:gcc.target/arm/arm.exp ... FAIL: gcc.target/arm/scd42-2.c scan-assembler mov[ \t].*272 Running gcc:gcc.target/arm/cmse/cmse.exp ... FAIL: gcc.target/arm/cmse/mainline/8_1m/bitfield-4.c -mcpu=unset -march=armv8.1-m.main+fp -mthumb -O2 scan-assembler lsls\t(r[3-9]|r10|fp|ip), \\1, #1.*blxns\t\\1 FAIL: gcc.target/arm/cmse/mainline/8_1m/bitfield-4.c -mcpu=unset -march=armv8.1-m.main+fp -mthumb -O2 scan-assembler lsrs\t(r[3-9]|r10|fp|ip), \\1, #1.*blxns\t\\1 FAIL: gcc.target/arm/cmse/mainline/8_1m/bitfield-4.c -mcpu=unset -march=armv8.1-m.main+fp -mthumb -O3 -g scan-assembler lsls\t(r[3-9]|r10|fp|ip), \\1, #1.*blxns\t\\1 FAIL: gcc.target/arm/cmse/mainline/8_1m/bitfield-4.c -mcpu=unset -march=armv8.1-m.main+fp -mthumb -O3 -g scan-assembler lsrs\t(r[3-9]|r10|fp|ip), \\1, #1.*blxns\t\\1 ... and 19 more entries improvements.sum: === gcc tests === Running gcc:gcc.target/arm/cmse/cmse.exp ... FAIL: gcc.target/arm/cmse/mainline/8_1m/bitfield-4.c -march=armv8.1-m.main+fp -mthumb -O3 -g scan-assembler lsrs\t(r[3-9]|r10|fp|ip), \\1, #1.*blxns\t\\1 FAIL: gcc.target/arm/cmse/mainline/8_1m/bitfield-4.c -march=armv8.1-m.main+fp -mthumb -O3 -g scan-assembler lsls\t(r[3-9]|r10|fp|ip), \\1, #1.*blxns\t\\1 FAIL: gcc.target/arm/cmse/mainline/8_1m/bitfield-4.c -march=armv8.1-m.main+fp -mthumb -O2 scan-assembler lsrs\t(r[3-9]|r10|fp|ip), \\1, #1.*blxns\t\\1 FAIL: gcc.target/arm/cmse/mainline/8_1m/bitfield-4.c -march=armv8.1-m.main+fp -mthumb -O2 scan-assembler lsls\t(r[3-9]|r10|fp|ip), \\1, #1.*blxns\t\\1 FAIL: gcc.target/arm/cmse/mainline/8_1m/bitfield-6.c -march=armv8.1-m.main+fp -mthumb -O2 scan-assembler lsrs\t(r[3-9]|r10|fp|ip), \\1, #1.*blxns\t\\1 FAIL: gcc.target/arm/cmse/mainline/8_1m/bitfield-6.c -march=armv8.1-m.main+fp -mthumb -O2 scan-assembler lsls\t(r[3-9]|r10|fp|ip), \\1, #1.*blxns\t\\1 FAIL: gcc.target/arm/cmse/mainline/8_1m/bitfield-6.c -march=armv8.1-m.main+fp -mthumb -O3 -g scan-assembler lsrs\t(r[3-9]|r10|fp|ip), \\1, #1.*blxns\t\\1 ... and 16 more entries I can't make any sense of this at all. After hours wasted trying to find the configuration information from the logs (it's there, but to the inexperienced user of your reports, it is buried far too deep), I'm still none-the-wiser. Hi Richard, Thanks for looking into this. Do send us a quick email if you can't immideatelly find what you are looking for. As our email says "We understand 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." Regarding adding configure information to our reports -- we are working on it. Great. Where do I find the dejagnu target-list information for a run? ie the site.exp file (or whatever the DEJAGNU environment variable points at). All I can see is that things like FAIL: gcc.target/arm/cmse/mainline/8_1m/bitfield-4.c -march=armv8.1-m.main+fp -mthumb -O2 scan-assembler lsrs\t(r[3-9]|r10|fp|ip), \\1, #1.*blxns\t\\1 have changed to FAIL: gcc.target/arm/cmse/mainline/8_1m/bitfield-4.c -mcpu=unset -march=armv8.1-m.main+fp -mthumb -O2 scan-assembler lsrs\t(r[3-9]|r10|fp|ip), \\1, #1.*blxns\t\\1 (ie that -mcpu=unset has been added to the test name). That's not a regression, it's a simple FAIL->FAIL Yes, that's correct. Unfortunately, when a FAILed test is renamed,
Regressions on master at commit r15-3861 vs commit r15-3857 on Linux/x86_64
Regressions on master at commit r15-3861 vs commit r15-3857 on Linux/x86_64 New failures: New passes: FAIL: gcc.dg/lto/save-temps c_lto_save-temps_0.o-c_lto_save-temps_0.o link, -O -flto -save-temps
Regressions on master at commit r15-3863 vs commit r15-3857 on Linux/i686
Regressions on master at commit r15-3863 vs commit r15-3857 on Linux/i686 New failures: FAIL: gcc.dg/pr109393.c scan-tree-dump-times optimized "return 1;" 3 New passes:
