linaro-toolchain

linaro-toolchain@lists.linaro.org

7 participants
5634 discussions

Re: [Linaro-TCWG-CI] gcc-16-3093-gc7de7ddbfae: 1 regression on aarch64

by Andrew Pinski

On Sun, Aug 10, 2025 at 3:22 PM <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-aarch64, after: > | commit gcc-16-3093-gc7de7ddbfae > | Author: Andrew Pinski <quic_apinski(a)quicinc.com> > | Date: Sun Jun 8 10:51:02 2025 -0700 > | > | forwprop: Change optimize_agr_copyprop into forward walk instead > of backwards > | > | While thinking about how to implement the rest of the copy prop > and makes sure not > | to introduce some compile time problems, optimize_agr_copyprop > should be changed > | into a forwproping rather than looking backwards. > | ... 10 lines of the commit log omitted. > > Produces 1 regression: > | > | regressions.sum: > | Running acats:chapter c4 ... > | FAIL: c41303a > > Used configuration : > *CI config* tcwg_gnu_native_check_gcc master-aarch64 > *configure and test flags:* none, autodetected on > aarch64-unknown-linux-gnu > > We track this bug report under > https://linaro.atlassian.net/browse/GNU-1648. Please let us know if you > have a fix. > I filed https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121494 and will be looking into later tonight or tomorrow. It also happens on s390x which gives me a hint of where to start to try to reproduce it on x86_64. Thanks, Andrew > > 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_gcc--master-aarch64-build/2… > 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_gcc--master-aarch64-build/2… > The list of [ignored] baseline and flaky failures are in > * > https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/2… > > Current build : > https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/2… > Reference build : > https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/2… > > Instruction to reproduce the build : > https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/gcc/sha1… > > Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git

1 day, 4 hours

Fwd: [llvm/llvm-project] [mlir][llvm] Add intrinsic arg and result attribute support (PR #150783)

by Tobias Gysi

Dear Linaro Team, I am looking for advice on how to reproduce a flang-arm64-windows-msvc LLVM build bot failure. I hope I ended up in the right place here. I had to revert a PR (https://github.com/llvm/llvm-project/pull/150783) that broke the flang-arm64-windows-msvc LLVM build bot in the morning due to some tablegen-related problem. I did prepare a reland PR ( https://github.com/llvm/llvm-project/pull/151125) that addresses a potential issue. However, since I did not see any other build bot failures and since I was not able to reproduce the problem locally, I wonder if there is a way to run the build bot on my reland PR? Alternatively, hints on how to reproduce the problem locally on a x86 Linux machine would be appreciated. Best, Tobias ---------- Forwarded message --------- From: LLVM Continuous Integration <notifications(a)github.com> Date: Tue, Jul 29, 2025 at 9:58 AM Subject: Re: [llvm/llvm-project] [mlir][llvm] Add intrinsic arg and result attribute support (PR #150783) To: llvm/llvm-project <llvm-project(a)noreply.github.com> Cc: Tobias Gysi <tobias.gysi(a)nextsilicon.com>, State change < state_change(a)noreply.github.com> *llvm-ci* left a comment (llvm/llvm-project#150783) <https://github.com/llvm/llvm-project/pull/150783#issuecomment-3131154498> LLVM Buildbot has detected a new failure on builder flang-arm64-windows-msvc running on linaro-armv8-windows-msvc-01 while building mlir at step 6 "test-build-unified-tree-check-mlir". Full details are available at: https://lab.llvm.org/buildbot/#/builders/207/builds/4441 Here is the relevant piece of the build log for the reference Step 6 (test-build-unified-tree-check-mlir) failure: test (failure) ******************** TEST 'MLIR :: Dialect/Bufferization/Transforms/one-shot-module-bufferize-analysis.mlir' FAILED ******************** Exit Code: 1 Command Output (stdout): -- # RUN: at line 1 c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir-opt.exe C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\llvm-project\mlir\test\Dialect\Bufferization\Transforms\one-shot-module-bufferize-analysis.mlir -one-shot-bufferize="bufferize-function-boundaries test-analysis-only" -split-input-file | c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\filecheck.exe C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\llvm-project\mlir\test\Dialect\Bufferization\Transforms\one-shot-module-bufferize-analysis.mlir # executed command: 'c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir-opt.exe' 'C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\llvm-project\mlir\test\Dialect\Bufferization\Transforms\one-shot-module-bufferize-analysis.mlir' '-one-shot-bufferize=bufferize-function-boundaries test-analysis-only' -split-input-file # .---command stderr------------ # | Assertion failed: implArgAndResultAttrsOpInterface && "`::mlir::CallOpInterface` expected its base interface `::mlir::ArgAndResultAttrsOpInterface` to be registered", file C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/mlir/include\mlir/Interfaces/CallInterfaces.h.inc, line 122 # | PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace. # | Stack dump: # | 0. Program arguments: c:\\users\\tcwg\\llvm-worker\\flang-arm64-windows-msvc\\build\\bin\\mlir-opt.exe C:\\Users\\tcwg\\llvm-worker\\flang-arm64-windows-msvc\\llvm-project\\mlir\\test\\Dialect\\Bufferization\\Transforms\\one-shot-module-bufferize-analysis.mlir "-one-shot-bufferize=bufferize-function-boundaries test-analysis-only" -split-input-file # | Exception Code: 0xC000001D # | #0 0x00007ff60737543c (c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir-opt.exe+0x1af543c) # | #1 0x00007ffff958ae50 (C:\WINDOWS\System32\ucrtbase.dll+0x7ae50) # | #2 0xff61fffff958ba5c # `----------------------------- # error: command failed with exit status: 0xc000001d # executed command: 'c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\filecheck.exe' 'C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\llvm-project\mlir\test\Dialect\Bufferization\Transforms\one-shot-module-bufferize-analysis.mlir' # .---command stderr------------ # | C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\llvm-project\mlir\test\Dialect\Bufferization\Transforms\one-shot-module-bufferize-analysis.mlir:23:17: error: CHECK-LABEL: expected string not found in input # | // CHECK-LABEL: func @extract_slice_fun( # | ^ # | <stdin>:1:1: note: scanning from here # | module { # | ^ # | <stdin>:1:3: note: possible intended match here # | module { # | ^ # | # | Input file: <stdin> # | Check file: C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\llvm-project\mlir\test\Dialect\Bufferization\Transforms\one-shot-module-bufferize-analysis.mlir # | # | -dump-input=help explains the following input dump. # | # | Input was: # | <<<<<< # | 1: module { # | label:23'0 X~~~~~~~~ error: no match found # | label:23'1 ? possible intended match # | 2: } # | label:23'0 ~~ # | 3: # | label:23'0 ~ # | 4: // ----- # | label:23'0 ~~~~~~~~~ # | >>>>>> # `----------------------------- # error: command failed with exit status: 1 ... Step 7 (test-build-unified-tree-check-flang) failure: test (failure) ******************** TEST 'Flang :: Intrinsics/math-codegen.fir' FAILED ******************** Exit Code: 2 Command Output (stdout): -- # RUN: at line 1 split-file C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\llvm-project\flang\test\Intrinsics\math-codegen.fir C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\tools\flang\test\Intrinsics\Output\math-codegen.fir.tmp # executed command: split-file 'C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\llvm-project\flang\test\Intrinsics\math-codegen.fir' 'C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\tools\flang\test\Intrinsics\Output\math-codegen.fir.tmp' # RUN: at line 5 fir-opt C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\tools\flang\test\Intrinsics\Output\math-codegen.fir.tmp/abs_fast.fir --fir-to-llvm-ir="target=x86_64-unknown-linux-gnu" | c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\filecheck.exe C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\tools\flang\test\Intrinsics\Output\math-codegen.fir.tmp/abs_fast.fir # executed command: fir-opt 'C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\tools\flang\test\Intrinsics\Output\math-codegen.fir.tmp/abs_fast.fir' --fir-to-llvm-ir=target=x86_64-unknown-linux-gnu # .---command stderr------------ # | Assertion failed: implArgAndResultAttrsOpInterface && "`::mlir::CallOpInterface` expected its base interface `::mlir::ArgAndResultAttrsOpInterface` to be registered", file C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/mlir/include\mlir/Interfaces/CallInterfaces.h.inc, line 122 # | PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace. # | Stack dump: # | 0. Program arguments: fir-opt C:\\Users\\tcwg\\llvm-worker\\flang-arm64-windows-msvc\\build\\tools\\flang\\test\\Intrinsics\\Output\\math-codegen.fir.tmp/abs_fast.fir --fir-to-llvm-ir=target=x86_64-unknown-linux-gnu # | Exception Code: 0xC000001D # | #0 0x00007ff777271f54 mlir::detail::FallbackTypeIDResolver::registerImplicitTypeID(class llvm::StringRef) (c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\fir-opt.exe+0x1331f54) # | #1 0x00007ffff958ae50 (C:\WINDOWS\System32\ucrtbase.dll+0x7ae50) # | #2 0xdd54fffff958ba5c # `----------------------------- # error: command failed with exit status: 0xc000001d # executed command: 'c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\filecheck.exe' 'C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\tools\flang\test\Intrinsics\Output\math-codegen.fir.tmp/abs_fast.fir' # .---command stderr------------ # | FileCheck error: '<stdin>' is empty. # | FileCheck command line: c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\filecheck.exe C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\tools\flang\test\Intrinsics\Output\math-codegen.fir.tmp/abs_fast.fir # `----------------------------- # error: command failed with exit status: 2 -- ******************** — Reply to this email directly, view it on GitHub <https://github.com/llvm/llvm-project/pull/150783#issuecomment-3131154498>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABW7H2HANJOPE6QLHGYKBD33K…> . You are receiving this because you modified the open/close state.Message ID: <llvm/llvm-project/pull/150783/c3131154498(a)github.com> -- This e-mail message and any attachments thereto are intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any retransmission, dissemination, copying or other use of, or taking of any action in reliance upon this information is prohibited. If you are not the intended addressee, please contact the sender immediately and delete the materials and information from your device and system and confirm the deletion by reply e-mail.

1 day, 20 hours

[Linaro-TCWG-CI] binutils-2_41-release-7632-g09292f4ae2c: 1 regression 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 binutils-2_41-release-7632-g09292f4ae2c | Author: Indu Bhagat <indu.bhagat(a)oracle.com> | Date: Tue Aug 19 01:08:06 2025 -0700 | | binutils: dwarf: fix display of large cfa_offset | | eh_frame textual dump was not correct when the cfa_offset is a large | value. The reason is that the dumping code generally assumes the | cfa_offset is an 'int'. | ... 31 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running gas:gas/cfi/cfi.exp ... | FAIL: CFI common 10 Used configuration : *CI config* tcwg_gnu_native_check_binutils 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-1658. 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_binutils--master-arm-build/… 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_binutils--master-arm-build/… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gnu_native_check_binutils--master-arm-build/… Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_binutils--master-arm-build/… Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_binutils--master-arm-build/… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/binut… Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=09292f4ae2ccb…

1 day, 21 hours

Re: [Linaro-TCWG-CI] llvmorg-22-init-6462-g35b22764e26a: 1 regression on aarch64

by Takahiro Kawashima (Fujitsu)

Hi, Probably this failure is a false detection caused by a floating-point precision error in fast-math. Please ignore the mail. We'll update the test. I apologize for the false detection. > 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-22-init-6462-g35b22764e26a > | Author: Hassnaa Hamdi <hassnaa.hamdi(a)arm.com> > | Date: Thu Sep 4 19:31:30 2025 +0100 > | > | [LV][AArch64] Prefer epilogue with fixed-width over scalable VF. (#155546) > | > | In case of equal costs Prefer epilogue with fixed-width over scalable VF. > | That is helpful in cases like post-LTO vectorization where epilogue with > | fixed-width VF can be removed when we eventually know that the trip count > | ... 1 lines of the commit log omitted. > > Produces 1 regression: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0136 ... > | FAIL: test-suite :: Fujitsu/Fortran/0136/Fujitsu-Fortran-0136_0012.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;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -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/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/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 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite" > > We track this bug report under https://linaro.atlassian.net/browse/LLVM-2090. 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://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/… > > Full commit : https://github.com/llvm/llvm-project/commit/35b22764e26aa02ef3ad849bb449bf7…

1 week

Re: [Linaro-TCWG-CI] llvmorg-22-init-6898-gdf430c33a71f: Failure on aarch64

by Nathan Chancellor

On Wed, Sep 10, 2025 at 05:23:47AM +0000, ci_notify(a)linaro.org wrote: > In tcwg_kernel/llvm-master-aarch64-stable-allyesconfig, after: > | commit llvmorg-22-init-6898-gdf430c33a71f > | Author: Nathan Chancellor <nathan(a)kernel.org> > | Date: Mon Sep 8 11:33:57 2025 -0700 > | > | [Frontend] Define __SANITIZE__ macros for kernel address variants (#156543) > | > | GCC defines these macros for both userspace and kernel address > | sanitizers: > | > | ... 29 lines of the commit log omitted. > > Produces Failure: > | Results changed to > | # reset_artifacts: > | -10 > | # build_abe binutils: > | -9 > | # build_kernel_llvm: > | -5 > | # build_abe qemu: > | -2 > | # linux_n_obj: > | 316 > | # First few build errors in logs: > | # 00:08:01 ./include/linux/compiler-clang.h:28:9: error: '__SANITIZE_ADDRESS__' macro redefined [-Werror,-Wmacro-redefined] > | # 00:08:01 ./include/linux/compiler-clang.h:28:9: error: '__SANITIZE_ADDRESS__' macro redefined [-Werror,-Wmacro-redefined] > | # 00:08:01 ./include/linux/compiler-clang.h:28:9: error: '__SANITIZE_ADDRESS__' macro redefined [-Werror,-Wmacro-redefined] > | # 00:08:01 ./include/linux/compiler-clang.h:28:9: error: '__SANITIZE_ADDRESS__' macro redefined [-Werror,-Wmacro-redefined] > | # 00:08:01 ./include/linux/compiler-clang.h:28:9: error: '__SANITIZE_ADDRESS__' macro redefined [-Werror,-Wmacro-redefined] > | # 00:08:01 ./include/linux/compiler-clang.h:28:9: error: '__SANITIZE_ADDRESS__' macro redefined [-Werror,-Wmacro-redefined] > | # 00:08:01 ./include/linux/compiler-clang.h:28:9: error: '__SANITIZE_ADDRESS__' macro redefined [-Werror,-Wmacro-redefined] > | # 00:08:01 ./include/linux/compiler-clang.h:28:9: error: '__SANITIZE_ADDRESS__' macro redefined [-Werror,-Wmacro-redefined] > | # 00:08:01 ./include/linux/compiler-clang.h:28:9: error: '__SANITIZE_ADDRESS__' macro redefined [-Werror,-Wmacro-redefined] > | # 00:08:01 ./include/linux/compiler-clang.h:28:9: error: '__SANITIZE_ADDRESS__' macro redefined [-Werror,-Wmacro-redefined] Thanks for the report. The kernel side fix for this has been picked up in a maintainer's tree [1] so it should be in Linus's tree soon then into stable shortly after that. This was already a problem in certain trees with CONFIG_KCSAN and __SANITIZE_THREAD__, I just made it a little worse ;) [1]: https://git.kernel.org/akpm/mm/c/3fac212fe489aa0dbe8d80a42a7809840ca7b0f9 Cheers, Nathan

1 week

Re: [Linaro-TCWG-CI] gcc-16-3649-gc440b585ba3: 4 regressions on master-thumb_m3_softfp_eabi

by Luc Grosheintz

I'd like to apologize for causing these regressions. Below I've copied out the relevant parts from the logs. To me it looks like _Xv is a reserved identifier. I'll prepare a patch to fix the issue. On 9/9/25 6:54 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 arm-eabi cortex-m3 softfp, after: > | commit gcc-16-3649-gc440b585ba3 > | Author: Luc Grosheintz <luc.grosheintz(a)gmail.com> > | Date: Thu Sep 4 14:20:28 2025 +0200 > | > | libstdc++: Implement constant_wrapper, cw from P2781R9. > | > | This is a partial implementation of P2781R9. It adds std::cw and > | std::constant_wrapper, but doesn't modify __integral_constant_like for > | span/mdspan. > | ... 25 lines of the commit log omitted. > > Produces 4 regressions: > | > | regressions.sum: > | Running g++:g++.old-deja/old-deja.exp ... > | FAIL: g++.old-deja/g++.robertl/eb39.C -std=c++26 (test for excess errors) Code: 4651: template<_CwFixedValue _Xv, typename> 4652: struct constant_wrapper : _CwOperators 4653: { Compiler error: /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/type_traits:4651:26: error: expected '>' before numeric constant My guess is that _Xv is a reserved name. It's not on the list of common bad identifiers [1], but it's the only guess I have. [1]: https://gcc.gnu.org/onlinedocs/libstdc++/manual/source_code_style.html > | FAIL: g++.old-deja/g++.robertl/eb54.C -std=c++26 (test for excess errors) Same as above. > | UNRESOLVED: g++.old-deja/g++.robertl/eb54.C -std=c++26 compilation failed to produce executable Same as above. > | FAIL: g++.old-deja/g++.warn/iomanip.C -std=gnu++26 (test for excess errors) Same as above. > Used configuration : > *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv7-m -mtune=cortex-m3 -mfloat-abi=softfp -mfpu=auto > *configure and test flags:* --target arm-eabi --disable-multilib --with-mode=thumb --with-cpu=cortex-m3 --with-float=softfp --target_board=-mthumb/-march=armv7-m/-mtune=cortex-m3/-mfloat-abi=softfp/-mfpu=auto qemu_cpu=cortex-m3 > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1676. 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_m3_softfp_… > 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_m3_softfp_… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m3_softfp_… > > Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m3_softfp_… > Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m3_softfp_… > > Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s… > > Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git

1 week

RE: [Linaro-TCWG-CI] llvmorg-22-init-6821-ga103b9b207f6: 1 regression on aarch64

by Jean Perier

Thanks for the report. There is also an LLVM issue tracking this. I commented there: https://github.com/llvm/llvm-project/issues/157763#issuecomment-3273773003 The test is violating F2023 C15121 that is not properly enforced by flang semantics but that lowering now relies on. Although we will likely improve LEN lowering which would have the side effect of working around the segfault in the specific case of 0727_0008, I think we will enforce C15121 in a manner that will reject it. See The LLVM link for more details and suggestion on how to fix the test. Jean Perier -----Original Message----- From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Sent: Wednesday, September 10, 2025 6:12 AM To: ohno.yasuyuki(a)fujitsu.com; itou.tetsuya(a)fujitsu.com; t-kawashima(a)fujitsu.com Cc: maxim.kuvyrkov(a)linaro.org; Jean Perier <jperier(a)nvidia.com> Subject: [Linaro-TCWG-CI] llvmorg-22-init-6821-ga103b9b207f6: 1 regression on aarch64 [You don't often get email from ci_notify(a)linaro.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] 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-O0-debug, after: | commit llvmorg-22-init-6821-ga103b9b207f6 | Author: jeanPerier <jperier(a)nvidia.com> | Date: Mon Sep 8 12:07:37 2025 +0200 | | [flang][lowering] fix vector subscripts in character elemental procedures (#156661) | | Fixes https://github.com/llvm/llvm-project/issues/145151 | | Character elemental procedures require evaluating the result | ... 22 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0727 ... | FAIL: test-suite :: Fujitsu/Fortran/0727/Fujitsu-Fortran-0727_0008.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;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -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/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O0 -g" -DCMAKE_CXX_FLAGS_RELEASE="-O0 -g" -DCMAKE_Fortran_FLAGS_RELEASE="-O0 -g" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" We track this bug report under https://linaro.atlassian.net/browse/LLVM-2088. 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-O0-debug-build/1378… 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-O0-debug-build/1378… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/1378… Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/1378… Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/1377… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/… Full commit : https://github.com/llvm/llvm-project/commit/a103b9b207f67e0afbaf41647a56a4c…

1 week

Re: [Linaro-TCWG-CI] llvmorg-22-init-6056-g89f53af3fffe: 3 regressions on aarch64

by Takahiro Kawashima (Fujitsu)

Hi, These errors are caused by incorrect test programs. Please ignore the mail. We'll update the tests. I apologize for the false detection. > 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-22-init-6056-g89f53af3fffe > | Author: Yingwei Zheng <dtcxzyw2333(a)gmail.com> > | Date: Tue Sep 2 21:41:02 2025 +0800 > | > | [ConstraintElim] Use constraints from bounded memory accesses (#155253) > | > | This patch removes bound checks that are dominated by bounded memory > | accesses. For example, if we have an array `int A[5]` and `A[idx]` is > | performed successfully, we know that `idx u< 5` after the load. > | ... 7 lines of the commit log omitted. > > Produces 3 regressions: > | > | regressions.sum: > | Running test-suite:Fujitsu/C/0094 ... > | FAIL: test-suite :: Fujitsu/C/0094/Fujitsu-C-0094_0040.test > | Running test-suite:Fujitsu/C/0137 ... > | FAIL: test-suite :: Fujitsu/C/0137/Fujitsu-C-0137_0280.test > | Running test-suite:Fujitsu/C/0170 ... > | ... and 1 more > | # "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;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -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/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/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 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite" > > We track this bug report under https://linaro.atlassian.net/browse/LLVM-2086. 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://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/… > > Full commit : https://github.com/llvm/llvm-project/commit/89f53af3fffed3e41167fbb7bc10d48…

1 week, 2 days

Re: [Linaro-TCWG-CI] llvmorg-22-init-5791-ga36c13492afa: 1 regression on aarch64

by Takahiro Kawashima (Fujitsu)

Hi, Probably this failure is a false detection caused by the fast-math flag. The test uses NaN and very large values. Appending -fhonor-nans -fhonor-infinities resolves the failure. Please ignore the mail. We'll update the test. Sorry for the noise. > 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_vla, after: > | commit llvmorg-22-init-5791-ga36c13492afa > | Author: Slava Zakharin <szakharin(a)nvidia.com> > | Date: Fri Aug 29 13:04:55 2025 -0700 > | > | [flang] Re-enable setting `noalias` on procedure arguments. (#155949) > | > | This is a follow-up on #140803, which was disabled in #142128 > | due to #143219. > > Produces 1 regression: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0351 ... > | FAIL: test-suite :: Fujitsu/Fortran/0351/Fujitsu-Fortran-0351_0099.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;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -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/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/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=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite" > > We track this bug report under https://linaro.atlassian.net/browse/LLVM-2081. 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_vla-build… > 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_vla-build… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > > Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ > > Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > > Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/… > > Full commit : https://github.com/llvm/llvm-project/commit/a36c13492afa64f925a9cf6ffe99534…

2 weeks

Re: [Linaro-TCWG-CI] llvmorg-22-init-5728-gf19b807a2362: 1 regression on aarch64

by Takahiro Kawashima (Fujitsu)

Hi, This error is caused by an incorrect test program. Please ignore the 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_vla, after: > | commit llvmorg-22-init-5728-gf19b807a2362 > | Author: Peter Klausler <pklausler(a)nvidia.com> > | Date: Fri Aug 29 07:49:09 2025 -0700 > | > | [flang] Extend error checking for implicit interfaces (#155473) > | > | When an external procedure is called by means of an implicit interface > | that turns out to be different in a significant way from the actual > | interface in its definition elsewhere in the source file, we emit an > | ... 5 lines of the commit log omitted. > > Produces 1 regression: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0178 ... > | NOEXE: test-suite :: Fujitsu/Fortran/0178/Fujitsu-Fortran-0178_0006.test > | # "NOEXE" means : the test program cannot be compiled > > Used configuration : > * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -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/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/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=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite" > > We track this bug report under https://linaro.atlassian.net/browse/LLVM-2079. 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_vla-build… > 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_vla-build… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > > Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ > > Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > > Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/… > > Full commit : https://github.com/llvm/llvm-project/commit/f19b807a23628776895cfc02f4a2938…

2 weeks, 2 days

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain