linaro-toolchain

linaro-toolchain@lists.linaro.org

3 participants
5603 discussions

[Linaro-TCWG-CI] glibc-2.41.9000-229-g7f163bd2106: 1 regressions on arm

by ci_notify＠linaro.org

Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In master-arm, after: | commit glibc-2.41.9000-229-g7f163bd2106 | Author: Joseph Myers <josmyers(a)redhat.com> | Date: Tue Apr 1 12:44:26 2025 +0000 | | Update syscall lists for Linux 6.14 | | Linux 6.14 has no new syscalls. Update the version number in | syscall-names.list to reflect that it is still current for 6.14. | | ... 1 lines of the commit log omitted. Produces 1 regressions: | | regressions.sum: | Running glibc:misc ... | FAIL: misc/tst-glibcsyscalls Used configuration : *CI config* tcwg_gnu_native_check_glibc master-arm *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf We track this bug report under https://linaro.atlassian.net/browse/GNU-1557. Please let us know if you have a fix. If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in *.log.1.xz files in * https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/112… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/112… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/112… Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/112… Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/111… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=7f163bd2106f96e2925e…

3 months

Re: [Linaro-TCWG-CI] gcc-15-9030-g78e0cf06c81: 5 regressions 4 improvements on master-thumb_m33_hard_eabi

by Sam James

ci_notify(a)linaro.org writes: > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In arm-eabi cortex-m33 hard, after: > | commit gcc-15-9030-g78e0cf06c81 > | Author: Sam James <sam(a)gentoo.org> > | Date: Sat Mar 29 21:09:25 2025 +0000 > | > | testsuite: arm: fixup more dg-final syntax > | > | ... as Richard E mentioned on the ML. Followup to r15-8956-ge90d6c2639c392. > | > | gcc/testsuite/ChangeLog: > | ... 2 lines of the commit log omitted. > > Produces 5 regressions 4 improvements: > | > | regressions.sum: > | Running gcc:gcc.target/arm/arm.exp ... > | FAIL: gcc.target/arm/short-vfp-1.c scan-assembler-times sxth\\tr[0-9]+,r[0-9]+ 2 > | FAIL: gcc.target/arm/short-vfp-1.c scan-assembler-times vcvt\\.f32\\.s32\\ts[0-9]+,s[0-9]+ 2 > | FAIL: gcc.target/arm/short-vfp-1.c scan-assembler-times vcvt\\.s32\\.f32\\ts[0-9]+,s[0-9]+ 2 > | FAIL: gcc.target/arm/short-vfp-1.c scan-assembler-times vmov\\tr[0-9]+,s[0-9]+ 2 > | ... and 1 more This one may need an ARM person to take a look at. (The issue was latent, and the test wasn't being run fully before.)

3 months

Re: [Linaro-TCWG-CI] llvmorg-21-init-6480-g529c5b71c608: 3 regressions 2 improvements on aarch64

by Kajetan Puchalski

Hi, I'm not familiar with the test suite in question, does it seem related to the test issue addressed in https://github.com/llvm/llvm-project/pull/133128? Or does it seem like it's caused by enabling the slp-vectorizer pass in the O3 pipeline where it was not enabled previously? ________________________________ Von: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Gesendet: Freitag, März 28, 2025 1:21:30 AM An: ohno.yasuyuki(a)fujitsu.com <ohno.yasuyuki(a)fujitsu.com>; itou.tetsuya(a)fujitsu.com <itou.tetsuya(a)fujitsu.com>; t-kawashima(a)fujitsu.com <t-kawashima(a)fujitsu.com> Cc: Kajetan Puchalski <Kajetan.Puchalski(a)arm.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org> Betreff: [Linaro-TCWG-CI] llvmorg-21-init-6480-g529c5b71c608: 3 regressions 2 improvements on aarch64 Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In tcwg_flang_test/main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays, after: | commit llvmorg-21-init-6480-g529c5b71c608 | Author: Kajetan Puchalski <kajetan.puchalski(a)arm.com> | Date: Wed Mar 26 16:10:35 2025 +0000 | | [flang] Add -f[no-]slp-vectorize flags (#132801) | | Add -f[no-]slp-vectorize to the flang driver. | Add corresponding -fvectorize-slp to the flang frontend. | | ... 6 lines of the commit log omitted. Produces 3 regressions 2 improvements: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0105 ... | NOEXE: test-suite :: Fujitsu/Fortran/0105/Fujitsu-Fortran-0105_0223.test | Running test-suite:Fujitsu/Fortran/0631 ... | FAIL: test-suite :: Fujitsu/Fortran/0631/Fujitsu-Fortran-0631_0051.test | FAIL: test-suite :: Fujitsu/Fortran/0631/Fujitsu-Fortran-0631_0054.test | # "NOEXE" means : the test program cannot be compiled | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one | | improvements.sum: | Running test-suite:Fujitsu/Fortran/0347 ... | FAIL: test-suite :: Fujitsu/Fortran/0347/Fujitsu-Fortran-0347_0083.test | Running test-suite:Fujitsu/Fortran/0675 ... | FAIL: test-suite :: Fujitsu/Fortran/0675/Fujitsu-Fortran-0675_0315.test | # "NOEXE" means : the test program cannot be compiled | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one Used configuration : * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld * Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH} cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG -fstack-arrays" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" We track this bug report under https://linaro.atlassian.net/browse/LLVM-1644. Please let us know if you have a fix. If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in *.log.1.xz files in * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_… Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_… Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… Full commit : https://github.com/llvm/llvm-project/commit/529c5b71c608c18141432e6fd0ae892… IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

3 months

Re: [Linaro-TCWG-CI] llvmorg-21-init-6604-gc6406c8dba33: 1 regressions on aarch64

by Takahiro Kawashima (Fujitsu)

Dear contributor, This FAIL is a floating-point precision error caused by the -ffast-math flag. Please ignore this mail. We'll update the test. > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld, after: > | commit llvmorg-21-init-6604-gc6406c8dba33 > | Author: David Green <david.green(a)arm.com> > | Date: Thu Mar 27 17:25:02 2025 +0000 > | > | [AArch64] Add getVectorInstrCost Codesize costs handling. (#130946) > | > | We have a lot of missing Codesize costs for vector operations. This > | patch starts things off by adding codesize costs for getVectorInstrCost, > | returning a single cost instead of the VectorInsertExtractBaseCost > | ... 2 lines of the commit log omitted. > > Produces 1 regressions: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0351 ... > | FAIL: test-suite :: Fujitsu/Fortran/0351/Fujitsu-Fortran-0351_0105.test > | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one > > Used configuration : > * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld > * Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH} > cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" > > We track this bug report under https://linaro.atlassian.net/browse/LLVM-1647. Please let us know if you have a fix. > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… > > Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ > > Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… > Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… > > Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > > Full commit : https://github.com/llvm/llvm-project/commit/c6406c8dba33d4cf8495257f70f52a2…

3 months

Re: [Linaro-TCWG-CI] gcc patch #109240: 2 regressions 2 improvements on arm

by Christophe Lyon

On Sat, 29 Mar 2025 at 22:07, <ci_notify(a)linaro.org> wrote: > > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In gcc_check master-arm, after: > | gcc patch https://patchwork.sourceware.org/patch/109240 > | Author: Richard Earnshaw <rearnsha(a)arm.com> > | Date: Wed Mar 26 17:19:11 2025 +0000 > | > | [PATCH] arm: don't vectorize fmaxf() unless unsafe math opts are enabled > | > | This test has presumably been failing since vectorization was enabled > | at -O2. I suspect part of the reason this wasn't picked up sooner is > | that the test is a hybrid execution/scan-assembler test and the > | ... 29 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 876a521a198 OpenMP: Fix declaration in append-args-interop.c test case > > Produces 2 regressions 2 improvements: > | > | regressions.sum: > | Running gcc:gcc.target/arm/arm.exp ... > | FAIL: gcc.target/arm/vect-fmaxmin.c scan-assembler-times vmaxnm.f32\tq[0-9]+, q[0-9]+, q[0-9]+ 1 > | FAIL: gcc.target/arm/vect-fmaxmin.c scan-assembler-times vminnm.f32\tq[0-9]+, q[0-9]+, q[0-9]+ 1 > | > | improvements.sum: > | Running gcc:gcc.target/arm/arm.exp ... > | FAIL: gcc.target/arm/fmaxmin.c scan-assembler-times vmaxnm.f32\ts[0-9]+, s[0-9]+, s[0-9]+ 1 > | FAIL: gcc.target/arm/fmaxmin.c scan-assembler-times vminnm.f32\ts[0-9]+, s[0-9]+, s[0-9]+ 1 > Hi Richard, I suspect the scripts were confused because there were some bugs in dg-directives during a few days, leading to random Tcl errors. You've committed your patch by now anyway, just mentioning in case you are confused. Thanks and sorry for the inconvenience, Christophe > Used configuration : > *CI config* tcwg_gcc_check master-arm > *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/11651/artifa… > 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-precommit/11651/artifa… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/11651/artifa… > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/11651/artifa… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3611/artifact/ar… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files.

3 months

Re: [Linaro-TCWG-CI] gcc-15-8965-gb631ff45f23: 2 regressions 2 improvements on arm

by Richard Earnshaw (lists)

On 29/03/2025 23:18, ci_notify(a)linaro.org wrote: > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In master-arm, after: > | commit gcc-15-8965-gb631ff45f23 > | Author: Richard Earnshaw <rearnsha(a)arm.com> > | Date: Wed Mar 26 15:56:18 2025 +0000 > | > | arm: don't vectorize fmaxf() unless unsafe math opts are enabled > | > | This test has presumably been failing since vectorization was enabled > | at -O2. I suspect part of the reason this wasn't picked up sooner is > | that the test is a hybrid execution/scan-assembler test and the > | ... 29 lines of the commit log omitted. > > Produces 2 regressions 2 improvements: > | > | regressions.sum: > | Running gcc:gcc.target/arm/arm.exp ... > | FAIL: gcc.target/arm/vect-fmaxmin.c scan-assembler-times vmaxnm.f32\tq[0-9]+, q[0-9]+, q[0-9]+ 1 > | FAIL: gcc.target/arm/vect-fmaxmin.c scan-assembler-times vminnm.f32\tq[0-9]+, q[0-9]+, q[0-9]+ 1 > | Fixed with r15-9064-gf30e180194bfbc R. > | improvements.sum: > | Running gcc:gcc.target/arm/arm.exp ... > | FAIL: gcc.target/arm/fmaxmin.c scan-assembler-times vminnm.f32\ts[0-9]+, s[0-9]+, s[0-9]+ 1 > | FAIL: gcc.target/arm/fmaxmin.c scan-assembler-times vmaxnm.f32\ts[0-9]+, s[0-9]+, s[0-9]+ 1 > > Used configuration : > *CI config* tcwg_gnu_cross_check_gcc master-arm > *configure and test flags:* --target arm-linux-gnueabihf > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1553. Please let us know if you have a fix. > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/1998/a… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/1998/a… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/1998/a… > > Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/1998/a… > Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/1997/a… > > Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=b631ff45f231db55b28b4c92c…

3 months

Re: [Linaro-TCWG-CI] gcc-15-8956-ge90d6c2639c: 8 regressions on aarch64

by Sam James

ci_notify(a)linaro.org writes: > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In gcc_check master-aarch64, after: > | commit gcc-15-8956-ge90d6c2639c > | Author: Sam James <sam(a)gentoo.org> > | Date: Thu Mar 27 00:21:43 2025 +0000 > | > | testsuite: more (mostly cosmetic) dg- whitespace fixes > | > | Some of these are harmless but still inconsistent (and asking for trouble > | given it may give people the wrong idea about similar "style"). > | > | ... 9 lines of the commit log omitted. > > Produces 8 regressions: > | > | regressions.sum: > | Running gcc:gcc.target/aarch64/aarch64.exp ... > | ERROR: tcl error code NONE > | ERROR: tcl error sourcing gcc.target/aarch64/aarch64.exp. > | UNRESOLVED: testcase gcc.target/aarch64/aarch64.exp' aborted due to Tcl error > | ERROR: unmatched open brace in list > | ... and 5 more Should be fixed with r15-8981-g176c7a2f751e04, thanks!

3 months

[committed] gcc/testsuite/g++.dg/gomp/append-args-8.C: Fix scan-dump-tree (was: [Linaro-TCWG-CI] gcc-15-8972-g7e286b56545: 3 regressions on aarch64)

by Tobias Burnus

The tree dump had bogus tailing numbers: interop.[0-9]+3, interop.[0-9]+2 This happened to work with x86-64 (-m32, -m64) but not with aarch64. I committed inr15-9033-ge0886d8ad4c519 the obvious fix: remove the 3 and 2 after the '+' Tobias ci_notify(a)linaro.org wrote: > In gcc_check master-aarch64, after: > | commit gcc-15-8972-g7e286b56545 > > We track this bug report underhttps://linaro.atlassian.net/browse/GNU-1554. Please let us know if you have a fix.

3 months, 1 week

Re: [Linaro-TCWG-CI] llvmorg-21-init-6198-g9694844d7e36: Failure on aarch64

by Nathan Chancellor

On Fri, Mar 28, 2025 at 03:28:46PM +0000, ci_notify(a)linaro.org wrote: > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In tcwg_kernel/llvm-master-aarch64-stable-allmodconfig, after: > | commit llvmorg-21-init-6198-g9694844d7e36 > | Author: Henry Jiang <h243jian(a)uwaterloo.ca> > | Date: Mon Mar 24 09:49:31 2025 -0400 > | > | Reland "[Transforms] LoopIdiomRecognize recognize strlen and wcslen #108985" (#132572) > | > | Reland https://github.com/llvm/llvm-project/pull/108985 > | > | Extend `LoopIdiomRecognize` to find and replace loops of the form > | ... 12 lines of the commit log omitted. Thanks a lot for the report. I sent the third version of the patchset that should resolve this issue this morning so I hope it will be moved on soon: https://lore.kernel.org/20250328-string-add-wcslen-for-llvm-opt-v3-0-a180b4… Cheers, Nathan

3 months, 1 week

Re: [Linaro-TCWG-CI] gcc-15-8947-g8ed2d5d219e: 5 regressions on master-thumb_m23_soft_eabi

by Christophe Lyon

Hi, On Fri, 28 Mar 2025 at 14:24, <ci_notify(a)linaro.org> wrote: > > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In arm-eabi cortex-m23 soft, after: > | commit gcc-15-8947-g8ed2d5d219e > | Author: Jørgen Kvalsvik <j(a)lambda.is> > | Date: Tue Jun 4 14:13:22 2024 +0200 > | > | Add prime path coverage to gcc/gcov > | > | This patch adds prime path coverage to gcc/gcov. First, a quick > | introduction to path coverage, before I explain a bit on the pieces of > | the patch. > | ... 404 lines of the commit log omitted. > > Produces 5 regressions: > | > | regressions.sum: > | Running g++:g++.dg/gcov/gcov.exp ... > | FAIL: g++.dg/gcov/gcov-22.C -std=gnu++17 gcov failed: spawn failed > | FAIL: g++.dg/gcov/gcov-22.C -std=gnu++26 gcov failed: spawn failed > | FAIL: g++.dg/gcov/gcov-22.C -std=gnu++98 gcov failed: spawn failed > | Running gcc:gcc.misc-tests/gcov.exp ... > | ... and 2 more > I've given a quick look at the logs, and gcov-22.C says: spawn -ignore SIGHUP /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/builds/destdir/x86_64-pc-linux-gnu/bin/gcov --prime-paths gcov-22.C FAIL: g++.dg/gcov/gcov-22.C -std=gnu++98 gcov failed: spawn failed I believe that rather than "dg-compile", it should use "dg-do run { target native }" like almost all other gcov tests? For the other errors: FAIL: gcc.misc-tests/gcov-31.c (test for excess errors) FAIL: gcc.misc-tests/gcov-32.c (test for excess errors) the log actually says: /gcov-31.c:12:8: error: unknown type name 'sigjmp_buf'; did you mean 'jmp_buf'? /gcov-31.c: In function 'run_pending_traps': /gcov-31.c:22:5: error: implicit declaration of function '__sigsetjmp' [-Wimplicit-function-declaration] /gcov-32.c:6:8: error: unknown type name 'sigjmp_buf'; did you mean 'jmp_buf'? /gcov-32.c:21:19: error: passing argument 1 of 'setjmp' makes pointer from integer without a cast [-Wint-conversion] I haven't looked further, but does this indicate a dependency on glibc? (this target "arm-none-eabi" uses newlib) Thanks, Christophe > Used configuration : > *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv8-m.base -mtune=cortex-m23 -mfloat-abi=soft -mfpu=auto > *configure and test flags:* --target arm-eabi --disable-multilib --with-mode=thumb --with-cpu=cortex-m23 --with-float=soft --target_board=-mthumb/-march=armv8-m.base/-mtune=cortex-m23/-mfloat-abi=soft/-mfpu=auto qemu_cpu=cortex-m33 > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1551. Please let us know if you have a fix. > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m23_soft_e… > 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_m23_soft_e… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m23_soft_e… > > Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m23_soft_e… > Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m23_soft_e… > > Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=8ed2d5d219e999aee42015a0d…

3 months, 1 week

← Newer
1
2
3
4
5
6
7
8
...
561
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain