-----Original Message----- From: ci_notify@linaro.org ci_notify@linaro.org Sent: Friday, December 29, 2023 7:40 AM To: Andrew Pinski (QUIC) quic_apinski@quicinc.com Cc: gcc-regression@gcc.gnu.org Subject: [Linaro-TCWG-CI] gcc-14-6861-g200531d5b9f: 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-toolchain@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-1091 , please let us know if you are looking at the problem and/or when you have a fix.
First I suspect this was failing before r14-6822-g01f4251b8775c8 and I just return it back to that state.
The big ask I have is for reports like this, to include the exact gcc configure line that was used. In this case, is GCC configured to include neon by default? If so then the testcase needs to be updated to add an option to disable neon. If not, then someone else will need to look into why the testcase is failing. Basically, the update I did was disable vectorization on a loop which was not being vectorized before r14-6822-g01f4251b8775c8.
Thanks, Andrew Pinski
In master-arm after:
| commit gcc-14-6861-g200531d5b9f | Author: Andrew Pinski quic_apinski@quicinc.com | Date: Thu Dec 28 20:26:01 2023 -0800 | | Fix gen-vect-26.c testcase after loops with multiple exits [PR113167] | | This fixes the gcc.dg/tree-ssa/gen-vect-26.c testcase by adding | `#pragma GCC novector` in front of the loop that is doing the checking | of the result. We only want to test the first loop to see if it can be | vectorize. | | ... 9 lines of the commit log omitted.
FAIL: 1 regressions
regressions.sum: === gcc tests ===
Running gcc:gcc.dg/tree-ssa/tree-ssa.exp ... FAIL: gcc.dg/tree-ssa/gen-vect-26.c scan-tree-dump-times vect "Alignment of access forced using peeling" 1
=== Results Summary ===You can find the failure logs in *.log.1.xz files in
build/1147/artifact/artifacts/00-sumfiles/ . The full lists of regressions and progressions are in
build/1147/artifact/artifacts/notify/ . The list of [ignored] baseline and flaky failures are in
build/1147/artifact/artifacts/sumfiles/xfails.xfail .
The configuration of this build is: CI config tcwg_gnu_cross_check_gcc master-arm
-----------------8<--------------------------8<--------------------------8<----------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master- arm-build/1147/artifact/artifacts Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc-- master-arm-build/1146/artifact/artifacts
Reproduce last good and first bad builds: https://git- us.linaro.org/toolchain/ci/interesting- commits.git/plain/gcc/sha1/200531d5b9fb99eca2b0d6b8d1e42d17641322 5f/tcwg_gnu_cross_check_gcc/master-arm/reproduction_instructions.txt
Full commit : https://github.com/gcc- mirror/gcc/commit/200531d5b9fb99eca2b0d6b8d1e42d176413225f
List of configurations that regressed due to this commit :
- tcwg_gnu_cross_check_gcc
** master-arm *** FAIL: 1 regressions *** https://git-us.linaro.org/toolchain/ci/interesting- commits.git/plain/gcc/sha1/200531d5b9fb99eca2b0d6b8d1e42d17641322 5f/tcwg_gnu_cross_check_gcc/master-arm/details.txt *** https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm- build/1147/artifact/artifacts
On Dec 30, 2023, at 06:24, Andrew Pinski (QUIC) via Gcc-regression gcc-regression@gcc.gnu.org wrote:
-----Original Message----- From: ci_notify@linaro.org ci_notify@linaro.org Sent: Friday, December 29, 2023 7:40 AM To: Andrew Pinski (QUIC) quic_apinski@quicinc.com Cc: gcc-regression@gcc.gnu.org Subject: [Linaro-TCWG-CI] gcc-14-6861-g200531d5b9f: 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-toolchain@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-1091 , please let us know if you are looking at the problem and/or when you have a fix.
First I suspect this was failing before r14-6822-g01f4251b8775c8 and I just return it back to that state.
The big ask I have is for reports like this, to include the exact gcc configure line that was used. In this case, is GCC configured to include neon by default? If so then the testcase needs to be updated to add an option to disable neon.
Hi Andrew,
We'll soon have configure and make info in the report.
If not, then someone else will need to look into why the testcase is failing. Basically, the update I did was disable vectorization on a loop which was not being vectorized before r14-6822-g01f4251b8775c8.
Ack.
Thanks,
-- Maxim Kuvyrkov https://www.linaro.org
Thanks, Andrew Pinski
In master-arm after:
| commit gcc-14-6861-g200531d5b9f | Author: Andrew Pinski quic_apinski@quicinc.com | Date: Thu Dec 28 20:26:01 2023 -0800 | | Fix gen-vect-26.c testcase after loops with multiple exits [PR113167] | | This fixes the gcc.dg/tree-ssa/gen-vect-26.c testcase by adding | `#pragma GCC novector` in front of the loop that is doing the checking | of the result. We only want to test the first loop to see if it can be | vectorize. | | ... 9 lines of the commit log omitted.
FAIL: 1 regressions
regressions.sum: === gcc tests ===
Running gcc:gcc.dg/tree-ssa/tree-ssa.exp ... FAIL: gcc.dg/tree-ssa/gen-vect-26.c scan-tree-dump-times vect "Alignment of access forced using peeling" 1
=== Results Summary ===
You can find the failure logs in *.log.1.xz files in
build/1147/artifact/artifacts/00-sumfiles/ . The full lists of regressions and progressions are in
build/1147/artifact/artifacts/notify/ . The list of [ignored] baseline and flaky failures are in
build/1147/artifact/artifacts/sumfiles/xfails.xfail .
The configuration of this build is: CI config tcwg_gnu_cross_check_gcc master-arm
-----------------8<--------------------------8<--------------------------8<----------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master- arm-build/1147/artifact/artifacts Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc-- master-arm-build/1146/artifact/artifacts
Reproduce last good and first bad builds: https://git- us.linaro.org/toolchain/ci/interesting- commits.git/plain/gcc/sha1/200531d5b9fb99eca2b0d6b8d1e42d17641322 5f/tcwg_gnu_cross_check_gcc/master-arm/reproduction_instructions.txt
Full commit : https://github.com/gcc- mirror/gcc/commit/200531d5b9fb99eca2b0d6b8d1e42d176413225f
List of configurations that regressed due to this commit :
- tcwg_gnu_cross_check_gcc
** master-arm *** FAIL: 1 regressions *** https://git-us.linaro.org/toolchain/ci/interesting- commits.git/plain/gcc/sha1/200531d5b9fb99eca2b0d6b8d1e42d17641322 5f/tcwg_gnu_cross_check_gcc/master-arm/details.txt *** https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm- build/1147/artifact/artifacts
linaro-toolchain@lists.linaro.org
-
Andrew Pinski (QUIC) -
Maxim Kuvyrkov