linaro-toolchain

linaro-toolchain@lists.linaro.org

12 participants
5687 discussions

Start a nNew thread

Re: [Linaro-TCWG-CI] gcc-16-372-g064cac730f8: 18 regressions on aarch64

by Sam James

See PR119930, PR120098, PR120101, PR120099.

10 months, 3 weeks

Windows builder issues

by Aaron Ballman

It looks like https://lab.llvm.org/buildbot/#/workers/149 is having problems: FAILED: bin/clang.exe C:\WINDOWS\system32\cmd.exe /C "cd . && C:\Users\tcwg\scoop\apps\cmake\3.30.1\bin\cmake.exe -E vs_link_exe --intdir=tools\clang\tools\driver\CMakeFiles\clang.dir --rc=C:\PROGRA~2\WI3CF2~1\10\bin\100226~1.0\x64\rc.exe --mt=C:\PROGRA~2\WI3CF2~1\10\bin\100226~1.0\x64\mt.exe --manifests -- C:\Users\tcwg\scoop\apps\llvm-arm64\current\bin\lld-link.exe /nologo @CMakeFiles\clang.rsp /out:bin\clang.exe /implib:lib\clang.lib /pdb:bin\clang.pdb /version:0.0 /machine:ARM64 /STACK:10000000 /INCREMENTAL:NO /subsystem:console && C:\WINDOWS\system32\cmd.exe /C "cd /D C:\Users\tcwg\llvm-worker\clang-arm64-windows-msvc\build\tools\clang\tools\driver && C:\Users\tcwg\scoop\apps\cmake\3.30.1\bin\cmake.exe -E copy C:/Users/tcwg/llvm-worker/clang-arm64-windows-msvc/build/bin/clang.exe C:/Users/tcwg/llvm-worker/clang-arm64-windows-msvc/build/./bin/clang++.exe && cd /D C:\Users\tcwg\llvm-worker\clang-arm64-windows-msvc\build\tools\clang\tools\driver && C:\Users\tcwg\scoop\apps\cmake\3.30.1\bin\cmake.exe -E copy C:/Users/tcwg/llvm-worker/clang-arm64-windows-msvc/build/bin/clang.exe C:/Users/tcwg/llvm-worker/clang-arm64-windows-msvc/build/./bin/clang-cl.exe && cd /D C:\Users\tcwg\llvm-worker\clang-arm64-windows-msvc\build\tools\clang\tools\driver && C:\Users\tcwg\scoop\apps\cmake\3.30.1\bin\cmake.exe -E copy C:/Users/tcwg/llvm-worker/clang-arm64-windows-msvc/build/bin/clang.exe C:/Users/tcwg/llvm-worker/clang-arm64-windows-msvc/build/./bin/clang-cpp.exe"" LINK: command "C:\Users\tcwg\scoop\apps\llvm-arm64\current\bin\lld-link.exe /nologo @CMakeFiles\clang.rsp /out:bin\clang.exe /implib:lib\clang.lib /pdb:bin\clang.pdb /version:0.0 /machine:ARM64 /STACK:10000000 /INCREMENTAL:NO /subsystem:console /MANIFEST:EMBED,ID=1" failed (exit code 1) with the following output: lld-link: error: failed to write output 'bin\clang.exe': permission denied Any chance you can look into it? Thanks! ~Aaron

10 months, 3 weeks

Re: [Linaro-TCWG-CI] glibc patch #111247: 90 regressions on arm

by Stefan Liebler

Hi, For this V2-patch, I got the same "Operation not permitted" errors as for the V1 one: https://lists.linaro.org/archives/list/linaro-toolchain@lists.linaro.org/th… @Adhemerval: have you had a look? The only non-s390x changes of my patch are in: elf/Makefile elf/tst-glibc-hwcaps-cache.script => There the libmarkermod6 libraries are added. As I don't have an arm, I've checked on x86_64, that the testcase elf/tst-glibc-hwcaps-cache.c contains the libmarkermod6.so files in glibc-hwcaps/z13-z17 directories by adding a "ldconfig -p" to the test. Any idea why those "Operation not permitted" regressions hits my patch, but no others? Bye, Stefan On 4/30/25 20:19, 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 glibc_check master-arm, after: > | glibc patch https://patchwork.sourceware.org/patch/111247 > | Author: Stefan Liebler <stli(a)linux.ibm.com> > | Date: Tue Apr 29 13:28:58 2025 +0200 > | > | [PATCH v2] S390: Add new s390 platform z17. > | > | Hi, > | need a V2: stfle_bits on stack in init_cpu_features_no_tunables() needs to be > | zeroed before usage. If there is no more feedback, I will commit this patch shortly. > | ... 41 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 84977600dac math: Fix UB on sinpif (BZ 32925) > > Produces 90 regressions: > | > | regressions.sum: > | Running glibc:debug ... > | FAIL: debug/tst-fortify-syslog > | Running glibc:dirent ... > | FAIL: dirent/tst-readdir-long > | FAIL: dirent/tst-readdir-zero-inode > | ... and 99 more > > Used configuration : > *CI config* tcwg_glibc_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_glibc_check--master-arm-precommit/3574/artif… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/3574/artif… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/3574/artif… > > Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/3574/artif… > Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2743/artifact/… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files.

10 months, 4 weeks

Re: [Linaro-TCWG-CI] gdb patch #111028: 2 regressions on arm

by Tom de Vries

On 4/30/25 06: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 gdb_check master-arm, after: > | gdb patch https://patchwork.sourceware.org/patch/111028 > | Author: Tom de Vries <tdevries(a)suse.de> > | Date: Fri Apr 25 17:13:32 2025 +0200 > | > | [PATCH v2] [gdb/testsuite] Simplify gdb.tui/tui-layout-asm.exp > | > | On x86_64-cygwin, with test-case gdb.tui/tui-layout-asm.exp I run into: > | ... > | WARNING: The following failure is probably due to the TUI window > | ... 49 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 48d0ac705c4 Handle base type without DW_AT_byte_size > > Produces 2 regressions: > | > | regressions.sum: > | Running gdb:gdb.python/py-missing-objfile.exp ... > | FAIL: gdb.python/py-missing-objfile.exp: initial sanity check: whatis global_exec_var > | FAIL: gdb.python/py-missing-objfile.exp: initial sanity check: whatis global_lib_var > The FAILs are obviously unrelated to the patch which modifies a different test-case. But anyway, this a know PR ( https://sourceware.org/bugzilla/show_bug.cgi?id=32445 ). I've just committed a fix. Thanks, - Tom > Used configuration : > *CI config* tcwg_gdb_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_gdb_check--master-arm-precommit/4439/artifac… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/4439/artifac… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/4439/artifac… > > Current build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/4439/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/2666/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.

11 months

Re: [Linaro-TCWG-CI] gcc-16-142-g01e5ef3e8b9: 2 regressions on arm

by Tomasz Kaminski

Hi, I have just pushed the following fix on trunk, that fixes a similar issue for 32bit x86_64. https://gcc.gnu.org/cgit/gcc/commit/?id=2ca5725e104d432317a44ad45183a4f555d… Please let me know if the build failure is addressed. Regards, Tomasz On Wed, Apr 30, 2025 at 5:14 AM <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: > | commit gcc-16-142-g01e5ef3e8b9 > | Author: Tomasz Kamiński <tkaminsk(a)redhat.com> > | Date: Wed Apr 23 13:17:09 2025 +0200 > | > | libstdc++: Minimalize temporary allocations when width is > specified [PR109162] > | > | When width parameter is specified for formatting range, tuple or > escaped > | presentation of string, we used to format characters to temporary > string, > | and write produce sequence padded according to the spec. However, > once the > | ... 53 lines of the commit log omitted. > > Produces 2 regressions: > | > | regressions.sum: > | Running libstdc++:libstdc++-dg/conformance.exp ... > | FAIL: std/format/debug.cc -std=gnu++23 execution test > | FAIL: std/format/debug.cc -std=gnu++26 execution test > > Used configuration : > *CI config* tcwg_gcc_check 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-1571. 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_gcc_check--master-arm-build/3771/artifact/ar… > 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/3771/artifact/ar… > The list of [ignored] baseline and flaky failures are in > * > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3771/artifact/ar… > > Current build : > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3771/artifact/ar… > Reference build : > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3770/artifact/ar… > > 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=01e5ef3e8b91288f5d387a277…

11 months

Re: [Linaro-TCWG-CI] gdb-16-branchpoint-1244-g5ea1eec52f4: 4 regressions 4 fixes on arm

by Tom de Vries

On 4/26/25 22:38, 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 gdb-16-branchpoint-1244-g5ea1eec52f4 > | Author: Tom de Vries <tdevries(a)suse.de> > | Date: Wed Apr 9 08:59:42 2025 +0200 > | > | [gdb/tdep] Handle ldaex and stlex in {thumb,arm}_deal_with_atomic_sequence_raw > | > | The Linaro CI reported a regression [1] in test-case > | gdb.base/step-over-syscall.exp due to commit 674d4856730 ("[gdb/testsuite] Fix > | gdb.base/step-over-syscall.exp with glibc 2.41"). > | ... 100 lines of the commit log omitted. > > Produces 4 regressions 4 fixes: > | > | regressions.sum: > | Running gdb:gdb.base/step-over-syscall.exp ... > | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: check_pc_after_cross_syscall: single step over fork final pc > | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: pc after stepi matches insn addr after syscall > | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=on: check_pc_after_cross_syscall: single step over fork final pc > | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=on: pc after stepi matches insn addr after syscall > | > | fixes.sum: > | Running gdb:gdb.base/step-over-syscall.exp ... > | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: continue to syscall insn fork (the program exited) > | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: find syscall insn in fork > | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: single step over fork (the program is no longer running) > | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: break on syscall insn > Hi, I've looked at this, and AFAICT this is PR32817 ( https://sourceware.org/bugzilla/show_bug.cgi?id=32817 ). This is unrelated to the mentioned commit. Thanks, - Tom > Used configuration : > *CI config* tcwg_gnu_native_check_gdb 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-1570. 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_gdb--master-arm-build/1993/… > 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_gdb--master-arm-build/1993/… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1993/… > > Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1993/… > Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1991/… > > Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sh… > > Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=5ea1eec52f47f…

11 months

[Linaro-TCWG-CI] glibc-2.41.9000-275-ge04afb7177: Failure on aarch64

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-aarch64, after: | commit glibc-2.41.9000-275-ge04afb7177 | Author: H. Peter Anvin <hpa(a)zytor.com> | Date: Fri Apr 25 07:30:59 2025 +0200 | | linux/termio: remove <termio.h> and struct termio | | The <termio.h> interface is absolutely ancient: it was obsoleted by | <termios.h> already in the first version of POSIX (1988) and thus | predates the very first version of Linux. Unfortunately, some constant | ... 15 lines of the commit log omitted. Produces Failure: | Results changed to | # reset_artifacts: | -10 | # true: | 0 | # build_abe binutils: | 1 | # build_abe stage1 --: | 2 | # build_abe linux: | 3 | # build_abe glibc: | 4 | # build_abe stage2 --: | # FAILED | # build_abe gdb: | # build_abe qemu: | # First few build errors in logs: | # 00:08:58 /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp:489:31: error: invalid application of ‘sizeof’ to incomplete type ‘__sanitizer::termio’ | # 00:08:58 make[4]: *** [Makefile:627: sanitizer_platform_limits_posix.lo] Error 1 | # 00:08:58 make[3]: *** [Makefile:533: all-recursive] Error 1 | # 00:08:58 make[2]: *** [Makefile:420: all] Error 2 | # 00:08:58 make[1]: *** [Makefile:12800: all-target-libsanitizer] Error 2 | # 00:08:58 make: *** [Makefile:1064: all] Error 2 | | From | # reset_artifacts: | -10 | # true: | 0 | # build_abe binutils: | 1 | # build_abe stage1 --: | 2 | # build_abe linux: | 3 | # build_abe glibc: | 4 | # build_abe stage2 --: | 5 | # build_abe gdb: | 6 | # build_abe qemu: | 7 Used configuration : *CI config* tcwg_gnu_cross_build master-aarch64 *configure and test flags:* --target aarch64-linux-gnu We track this bug report under https://linaro.atlassian.net/browse/GNU-1569. 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 * https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-build/1084/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_build--master-aarch64-build/1084/a… Current build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-build/1084/a… Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-build/1083/a… 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=e04afb71771710cdc602…

11 months

Adjust 'libgomp.c++/target-exceptions-pr118794-1.C' for 'targetm.arm_eabi_unwinder' [PR118794] (was: [Linaro-TCWG-CI] gcc-15-9463-gaa3e72f9430: 2 regressions on arm)

by Thomas Schwinge

Hi! On 2025-04-17T18:15:50+0000, ci_notify--- via Gcc-regression <gcc-regression(a)gcc.gnu.org> wrote: > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In bootstrap_check master-arm-check_bootstrap, after: > | commit gcc-15-9463-gaa3e72f9430 > | Author: Thomas Schwinge <tschwinge(a)baylibre.com> > | Date: Thu Mar 27 23:06:37 2025 +0100 > | > | Add test cases for exception handling constructs in dead code for GCN, nvptx target and OpenMP 'target' offloading [PR118794] > | > | PR target/118794 > | gcc/testsuite/ > | * g++.target/gcn/exceptions-pr118794-1.C: New. > | ... 7 lines of the commit log omitted. > > Produces 2 regressions: > | > | regressions.sum: > | Running libgomp:libgomp.c++/c++.exp ... > | FAIL: libgomp.c++/target-exceptions-pr118794-1.C scan-tree-dump-times optimized "gimple_call <__builtin_eh_pointer, " 1 > | FAIL: libgomp.c++/target-exceptions-pr118794-1.C scan-tree-dump-times optimized "gimple_call <__builtin_unwind_resume, " 1 Ah, sorry for that. This is due to 'targetm.arm_eabi_unwinder', as per: gcc/config/arm/arm.cc:#define TARGET_ARM_EABI_UNWINDER true gcc/config/c6x/c6x.cc:#define TARGET_ARM_EABI_UNWINDER true ..., which for ARM is conditional to '#if ARM_UNWIND_INFO' (defined in 'gcc/config/arm/bpabi.h', used for various GCC configurations), and for C6x unconditional. This gets us: --- target-exceptions-pr118794-1.C.269t.optimized +++ target-exceptions-pr118794-1.C.270t.optimized [...] __attribute__((omp declare target)) void f () [...] gimple_call <__dt_comp , NULL, &c> - gimple_call <__builtin_eh_pointer, _7, 2> - gimple_call <__builtin_unwind_resume, NULL, _7> + gimple_call <__builtin_cxa_end_cleanup, NULL> } [...] There doesn't appear to be an effective-target keyword for 'targetm.arm_eabi_unwinder' specifically, do we need to add one? Or, other test cases appear to use effective-target 'arm_eabi' to disambiguate the two variants; is that the right thing to use here, too? (..., plus 'tic6x-*-*' in this case?) OK to push the attached "Adjust 'libgomp.c++/target-exceptions-pr118794-1.C' for 'targetm.arm_eabi_unwinder' [PR118794]"? (Could Arm/C6x maintainers please test this for me?) Grüße Thomas > Used configuration : > *CI config* tcwg_bootstrap_check master-arm-check_bootstrap > *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1562. 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_bootstrap_check--master-arm-check_bootstrap-… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_bootstrap_check--master-arm-check_bootstrap-… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_bootstrap_check--master-arm-check_bootstrap-… > > Current build : https://ci.linaro.org/job/tcwg_bootstrap_check--master-arm-check_bootstrap-… > Reference build : https://ci.linaro.org/job/tcwg_bootstrap_check--master-arm-check_bootstrap-… > > 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=aa3e72f943032e5f074b2bd2f…

11 months, 1 week

Re: [Linaro-TCWG-CI] glibc patch #110503: 90 regressions on arm

by Stefan Liebler

Hi, I've looked into tests.log.1.xz and there are plenty of "Operation not permitted" errors. I don't think that this has something to do with my patch? Can you please check on your side, if there was a change/issue on the build system? Bye, Stefan On 4/16/25 13:32, 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 glibc_check master-arm, after: > | glibc patch https://patchwork.sourceware.org/patch/110503 > | Author: Stefan Liebler <stli(a)linux.ibm.com> > | Date: Tue Apr 15 16:52:17 2025 +0200 > | > | [PATCH] S390: Add new s390 platform z17. > | > | The glibc-hwcaps subdirectories are extended by "z17". Libraries are loaded if > | the z17 facility bits are active: > | - Miscellaneous-instruction-extensions facility 4 > | ... 35 lines of the commit log omitted. > | ... applied on top of baseline commit: > | ceeffd970c5 aarch64: Add back non-temporal load/stores from oryon-1's memset > > Produces 90 regressions: > | > | regressions.sum: > | Running glibc:debug ... > | FAIL: debug/tst-fortify-syslog > | Running glibc:dirent ... > | FAIL: dirent/tst-readdir-long > | FAIL: dirent/tst-readdir-zero-inode > | ... and 99 more > > Used configuration : > *CI config* tcwg_glibc_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_glibc_check--master-arm-precommit/3528/artif… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/3528/artif… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/3528/artif… > > Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/3528/artif… > Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2681/artifact/… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files.

11 months, 1 week

Re: [Linaro-TCWG-CI] llvmorg-21-init-8019-g0ae9bb96d5af: 86 regressions 14 fixes on aarch64

by Peter Klausler

The HTML links in your mail aren’t usable in my locked-down corporate e-mail environment. If you could just send me a list of the names of the 83 failing Fujitsu tests, I’ll look at them immediately. (The initial ones that are quoted in the mail are working now with llvm-project/main, but I’d like to check the others.) From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Date: Monday, April 14, 2025 at 20:36 To: 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: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>, Peter Klausler <pklausler(a)nvidia.com> Subject: [Linaro-TCWG-CI] llvmorg-21-init-8019-g0ae9bb96d5af: 86 regressions 14 fixes on aarch64 External email: Use caution opening links or attachments 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-8019-g0ae9bb96d5af | Author: Peter Klausler <pklausler(a)nvidia.com> | Date: Wed Apr 9 12:30:33 2025 -0700 | | [flang][OpenMP] Fix regression in !$\ continuation (#134756) | | A recent patch that obviated the need to use -fopenmp when using the | compiler to preprocess in -E mode broke a case of Fortran line | continuation when using OpenMP conditional compilation lines (!$\) when | ... 1 lines of the commit log omitted. Produces 86 regressions 14 fixes: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/1008 ... | NOEXE: test-suite :: Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0001.test | NOEXE: test-suite :: Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0002.test | NOEXE: test-suite :: Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0006.test | NOEXE: test-suite :: Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0008.test | ... and 84 more | # "NOEXE" means : the test program cannot be compiled | | fixes.sum: | Running test-suite:Fujitsu/Fortran/0213 ... | NOEXE: test-suite :: Fujitsu/Fortran/0213/Fujitsu-Fortran-0213_0029.test | NOEXE: test-suite :: Fujitsu/Fortran/0213/Fujitsu-Fortran-0213_0023.test | NOEXE: test-suite :: Fujitsu/Fortran/0213/Fujitsu-Fortran-0213_0018.test | NOEXE: test-suite :: Fujitsu/Fortran/0213/Fujitsu-Fortran-0213_0024.test | ... and 10 more | # "NOEXE" means : the test program cannot be compiled 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://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinaro.at…<https://linaro.atlassian.net/browse/LLVM-1665>. 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://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<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://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<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://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…> Fujitsu testsuite : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…<https://github.com/fujitsu/compiler-test-suite/> Current build : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…> Reference build : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…> Instruction to reproduce the build : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit-us.li…<https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…> Full commit : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…<https://github.com/llvm/llvm-project/commit/0ae9bb96d5af47a2426596dbd0c35e3…>

11 months, 2 weeks

← Newer
1
...
9
10
11
12
13
14
15
...
569
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain