On Mon, Jun 9, 2025 at 10:02 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 glibc_check master-aarch64, after:
> | glibc patch https://patchwork.sourceware.org/patch/113987
> | Author: H.J. Lu <hjl.tools(a)gmail.com>
> | Date: Mon Jun 9 05:22:10 2025 +0800
> |
> | [PATCH] i386: Update ___tls_get_addr to preserve vector registers
> |
> | Compiler generates the following instruction sequence for dynamic TLS
> | access:
> |
> | ... 44 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 0a027674a10 x86: Avoid GLRO(dl_x86_cpu_features)
>
> Produces 1 regression:
> |
> | regressions.sum:
> | Running glibc:elf ...
> | FAIL: elf/tst-tls23
So, this is a run-time failure. What happens if you run it by hand?
> Used configuration :
> *CI config* tcwg_glibc_check master-aarch64
> *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu
>
> 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-aarch64-precommit/3701/a…
> 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-aarch64-precommit/3701/a…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-precommit/3701/a…
>
> Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-precommit/3701/a…
> Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2930/artif…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
--
H.J.
Hi Cameron,
Someone happened to trigger a rebuild of enough of the files to get the bot
green again over the weekend. I don't understand exactly how they did it
though.
I would have thought a clean build would reset it but the first green was
not a clean build. We are using ccache and they are pre-*compiled* headers
so I guess it does cache them. ccache has recommendations (
https://ccache.dev/manual/latest.html#_precompiled_headers) that I don't
know that we have followed though.
Did you get any mail from our Linux buildbots? If PCH is enabled on
Windows, it should be on Linux too, I don't see where we disable it at
least.
Thanks,
David Spickett.
On Sat, 7 Jun 2025 at 00:08, Cameron McInally <cameron.mcinally(a)nyu.edu>
wrote:
> Hi Linaro folks,
>
> It appears my latest commit has broken your BuildBot:
>
> fatal error: file
>
> 'C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\llvm-project\llvm\include\llvm\Support\Compiler.h'
> has been modified since the precompiled header
>
> 'C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/./cmake_pch.cxx.pch'
> was built: size changed (was 26948, now 27102)
> note: please rebuild precompiled header
>
> 'C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/./cmake_pch.cxx.pch'
>
> I'm not sure if it's possible for me to rebuild the precompiled header
> myself. Any suggestions on how to proceed?
>
> Thanks in advance,
> Cameron
>
> ---------- Forwarded message ---------
> From: <llvm.buildmaster(a)lab.llvm.org>
> Date: Fri, Jun 6, 2025 at 6:13 PM
> Subject: ☠ Buildbot (LLVM Buildbot): flang-arm64-windows-msvc - failed
> build (failure) (main)
> To: Cameron McInally <cameron.mcinally(a)nyu.edu>, Thurston Dang
> <thurston(a)google.com>
> Cc: <llvm.buildmaster(a)lab.llvm.org>
>
>
> The Buildbot has detected a new failure on builder
> flang-arm64-windows-msvc while building clang.
>
> Full details are available at:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lab.llvm.org_buildbot_…
>
> Worker for this Build: linaro-armv8-windows-msvc-01
> Blamelist:
> Cameron McInally <cameron.mcinally(a)nyu.edu>,
> Thurston Dang <thurston(a)google.com>
>
> BUILD FAILED: failed build (failure)
>
> Step 5 (build-unified-tree) failure: build (failure)
> ...
> 378.972 [2600/10/4115] Building CXX object
> tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/char-set.cpp.obj
> 380.006 [2599/10/4116] Building CXX object
> tools/flang/lib/Evaluate/CMakeFiles/FortranEvaluate.dir/cmake_pch.cxx.obj
> 380.596 [2598/10/4117] Building AArch64GenInstrInfo.inc...
> 381.268 [2597/10/4118] Building CXX object
> tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/char-buffer.cpp.obj
> 382.326 [2596/10/4119] Building CXX object
> tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/debug-parser.cpp.obj
> 382.422 [2595/10/4120] Building CXX object
> tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/characters.cpp.obj
> 382.547 [2594/10/4121] Building AArch64GenSubtargetInfo.inc...
> 383.755 [2593/10/4122] Building CXX object
>
> tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/instrumented-parser.cpp.obj
> 385.992 [2592/10/4123] Building CXX object
> tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/message.cpp.obj
> 388.630 [2591/10/4124] Building CXX object
> tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/preprocessor.cpp.obj
> FAILED:
> tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/preprocessor.cpp.obj
> ccache C:\Users\tcwg\scoop\apps\llvm-arm64\current\bin\clang-cl.exe
> /nologo -TP -DFLANG_INCLUDE_TESTS=1 -DGTEST_HAS_RTTI=0 -DUNICODE
> -D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_NONSTDC_NO_WARNINGS
> -D_CRT_SECURE_NO_DEPRECATE -D_CRT_SECURE_NO_WARNINGS
> -D_GLIBCXX_ASSERTIONS -D_HAS_EXCEPTIONS=0 -D_SCL_SECURE_NO_DEPRECATE
> -D_SCL_SECURE_NO_WARNINGS -D_UNICODE -D__STDC_CONSTANT_MACROS
> -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS
>
> -IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/lib/Parser
>
> -IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/flang/lib/Parser
>
> -IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/flang/include
>
> -IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/include
> -IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/include
>
> -IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/llvm/include
>
> -imsvcC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/flang/../mlir/include
> -imsvcC:/Users/tcw
> g/llvm-worker/flang-arm64-windows-msvc/build/tools/mlir/include
>
> -imsvcC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/clang/include
>
> -imsvcC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/llvm/../clang/include
> /DWIN32 /D_WINDOWS /Zc:inline /Zc:__cplusplus /Oi /Brepro /bigobj
> /permissive- -Werror=unguarded-availability-new /W4 -Wextra
> -Wno-unused-parameter -Wwrite-strings -Wcast-qual
> -Wmissing-field-initializers -Wimplicit-fallthrough
> -Wcovered-switch-default -Wno-noexcept-type -Wnon-virtual-dtor
> -Wdelete-non-virtual-dtor -Wsuggest-override -Wstring-conversion
> -Wmisleading-indentation -Wctad-maybe-unsupported /Gw
> -Wno-deprecated-copy -Wno-string-conversion
> -Wno-ctad-maybe-unsupported -Xclang -fno-pch-timestamp /O2 /Ob2
> -std:c++17 -MD /EHs-c- /GR- -UNDEBUG
>
> /YuC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/cmake_pch.hxx
> /FpC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/
> lib/Parser/CMakeFiles/FortranParser.dir/./cmake_pch.cxx.pch
>
> /FIC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/cmake_pch.hxx
> /showIncludes
> /Fotools/flang/lib/Parser/CMakeFiles/FortranParser.dir/preprocessor.cpp.obj
> /Fdtools\flang\lib\Parser\CMakeFiles\FortranParser.dir\FortranParser.pdb
> -c --
> C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/flang/lib/Parser/preprocessor.cpp
> fatal error: file
>
> 'C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\llvm-project\llvm\include\llvm\Support\Compiler.h'
> has been modified since the precompiled header
>
> 'C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/./cmake_pch.cxx.pch'
> was built: size changed (was 26948, now 27102)
> note: please rebuild precompiled header
>
> 'C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/./cmake_pch.cxx.pch'
> 1 error generated.
> 392.025 [2591/9/4125] Building CXX object
> tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/prescan.cpp.obj
> 393.052 [2591/8/4126] Building CXX object
> tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/parsing.cpp.obj
> 393.434 [2591/7/4127] Building CXX object
> tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/parse-tree.cpp.obj
> 395.861 [2591/6/4128] Building CXX object
> tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/expr-parsers.cpp.obj
> 402.121 [2591/5/4129] Building CXX object
> tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/io-parsers.cpp.obj
> 408.915 [2591/4/4130] Building CXX object
> tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/openacc-parsers.cpp.obj
> 412.795 [2591/3/4131] Building CXX object
>
> tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/executable-parsers.cpp.obj
> 425.616 [2591/2/4132] Building CXX object
> tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/Fortran-parsers.cpp.obj
> 437.843 [2591/1/4133] Building CXX object
> tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/openmp-parsers.cpp.obj
> ninja: build stopped: subcommand failed.
>
> Sincerely,
> LLVM Buildbot
>
On Fri, 6 Jun 2025 at 18:17, <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-1247-gbdae7824cd9
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Wed Jun 4 15:53:20 2025 +0100
> |
> | libstdc++: Optimize std::counting_semaphore for futex path
> |
> | Rename __semaphore_base to __semaphore_impl, because it's not used as a
> | base class. Replace the three identical lambda expressions with a named
> | class, __semaphore_impl::_Available, which stores the most recent
> | ... 27 lines of the commit log omitted.
>
> Produces 7 regressions:
> |
> | regressions.sum:
> | Running g++:g++.dg/modules/modules.exp ...
> | FAIL: g++.dg/modules/xtreme-header-2_b.C -std=c++26 (test for excess errors)
> | FAIL: g++.dg/modules/xtreme-header-5_b.C -std=c++26 (test for excess errors)
> | FAIL: g++.dg/modules/xtreme-header-6_b.C -std=c++26 (test for excess errors)
> | FAIL: g++.dg/modules/xtreme-header-7_b.C -std=c++26 (test for excess errors)
> | ... and 3 more
>
> 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-1598. Please let us know if you have a fix.
It should be fixed at r16-1270-g7407891a3d7c17
>
> 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/3946/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/3946/artifact/ar…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3946/artifact/ar…
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3946/artifact/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3945/artifact/ar…
>
> 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
On Wed, 4 Jun 2025 at 02:50, <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_eabi, after:
> | commit gcc-16-427-g86627faec10d
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Fri Apr 25 21:09:18 2025 +0100
> |
> | libstdc++: Rewrite atomic builtin checks [PR70560]
> |
> | Currently the GLIBCXX_ENABLE_ATOMIC_BUILTINS macro checks for a variety
> | of __atomic built-ins for bool, short and int. If all those checks pass,
> | then it defines _GLIBCXX_ATOMIC_BUILTINS and uses the definitions from
> | ... 80 lines of the commit log omitted.
>
> Produces 11 regressions:
> |
> | regressions.sum:
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: 19_diagnostics/stacktrace/current.cc -std=gnu++23 (test for excess errors)
> | FAIL: 19_diagnostics/stacktrace/current.cc -std=gnu++26 (test for excess errors)
> | FAIL: 19_diagnostics/stacktrace/entry.cc -std=gnu++23 (test for excess errors)
> | FAIL: 19_diagnostics/stacktrace/entry.cc -std=gnu++26 (test for excess errors)
> | ... and 7 more
>
> Used configuration :
> *CI config* tcwg_gnu_embed_check_gcc master-arm_eabi
> *configure and test flags:* --target arm-eabi
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1595. Please let us know if you have a fix.
I've opened https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120567 for this.
>
> 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-arm_eabi-build/1…
> 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-arm_eabi-build/1…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/1…
>
> Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/1…
> Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/1…
>
> Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/gcc/sha1…
>
> Full commit : https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=86627faec10da53d753280501…
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_kernel/gnu-master-aarch64-mainline-allmodconfig, after:
| commit gcc-16-1028-g9739ae9384d
| Author: Andrew Pinski <quic_apinski(a)quicinc.com>
| Date: Thu May 29 23:50:08 2025 -0700
|
| Have TODO_verify_* not set by any pass
|
| This is a follow up to the patch set starting at https://gcc.gnu.org/pipermail/gcc-patches/2014-April/386650.html.
|
| Currently TODO_verify_{il,all} is set by a few passes as TODOs afterwards but
| ... 32 lines of the commit log omitted.
Produces Failure:
| Results changed to
| # reset_artifacts:
| -10
| # build_abe binutils:
| -9
| # build_abe stage1:
| -5
| # build_abe qemu:
| -2
| # linux_n_obj:
| 30
| # First few build errors in logs:
| # 00:05:59 scripts/gcc-plugins/gcc-common.h:176:25: error: ‘TODO_verify_il’ was not declared in this scope; did you mean ‘TODO_verify_flow’?
| # 00:05:59 scripts/gcc-plugins/gcc-common.h:176:25: error: ‘TODO_verify_il’ was not declared in this scope; did you mean ‘TODO_verify_flow’?
| # 00:05:59 scripts/gcc-plugins/gcc-common.h:178:27: error: ‘TODO_verify_il’ was not declared in this scope; did you mean ‘TODO_verify_flow’?
| # 00:06:00 scripts/gcc-plugins/gcc-common.h:177:26: error: ‘TODO_verify_il’ was not declared in this scope; did you mean ‘TODO_verify_flow’?
| # 00:06:00 make[3]: *** [scripts/gcc-plugins/Makefile:54: scripts/gcc-plugins/latent_entropy_plugin.so] Error 1
| # 00:06:00 scripts/gcc-plugins/gcc-common.h:178:27: error: ‘TODO_verify_il’ was not declared in this scope; did you mean ‘TODO_verify_flow’?
| # 00:06:00 scripts/gcc-plugins/gcc-common.h:176:25: error: ‘TODO_verify_il’ was not declared in this scope; did you mean ‘TODO_verify_flow’?
| # 00:06:00 scripts/gcc-plugins/gcc-common.h:178:27: error: ‘TODO_verify_il’ was not declared in this scope; did you mean ‘TODO_verify_flow’?
| # 00:06:01 make[3]: *** [scripts/gcc-plugins/Makefile:54: scripts/gcc-plugins/stackleak_plugin.so] Error 1
| # 00:06:03 make[2]: *** [scripts/Makefile.build:461: scripts/gcc-plugins] Error 2
|
| From
| # reset_artifacts:
| -10
| # build_abe binutils:
| -9
| # build_abe stage1:
| -5
| # build_abe qemu:
| -2
| # linux_n_obj:
| 36872
| # linux build successful:
| all
Used configuration :
tcwg_kernel/gnu-master-aarch64-mainline-allmodconfig
We track this bug report under https://linaro.atlassian.net/browse/GNU-1592. 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:
Current build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-mainline-allmodco…
Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-mainline-allmodco…
Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/gcc/sha1…
Full commit : https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=9739ae9384dd7cd3bb1c7683d…
Hi,
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.
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_vls-lto-lld, after:
> | commit llvmorg-21-init-13711-ga0d699a8e686
> | Author: Slava Zakharin <szakharin(a)nvidia.com>
> | Date: Wed May 28 17:18:04 2025 -0700
> |
> | Reland "[flang] Added noalias attribute to function arguments. (#140803)"
> |
> | This helps to disambiguate accesses in the caller and the callee
> | after LLVM inlining in some apps. I did not see any performance
> | changes, but this is one step towards enabling other optimizations
> | ... 14 lines of the commit log omitted.
>
> Produces 2 regressions:
> |
> | regressions.sum:
> | Running test-suite:Fujitsu/Fortran/0122 ...
> | FAIL: test-suite :: Fujitsu/Fortran/0122/Fujitsu-Fortran-0122_0045.test
> | FAIL: test-suite :: Fujitsu/Fortran/0122/Fujitsu-Fortran-0122_0048.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-1691. 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/Linaro/tcwg/ci/interesting-commits/-/raw/master/llvm/sha…
>
> Full commit : https://github.com/llvm/llvm-project/commit/a0d699a8e686cba99690cf28463d145…
Hi all.
I got an automated mail about this GCC regression related to one of my commits.
https://linaro.atlassian.net/browse/GNU-1578
The mail itself mentioned only a testsuite regression. I fixed that. However,
this was also linked in the mail:
https://ci.linaro.org/job/tcwg_bootstrap_build--master-arm-bootstrap_profil…
That looks like a different regression. As far as I can tell, `make
profiledbootstrap` is failing on arm. I have only very limited access to arm
machines. I tried to reproduce this on an Aarch64 machine and didn't succeed.
Could you check that this regression is still present on current trunk and/or
help me reproduce it?
Btw the "Instructions to reproduce the build" link doesn't work for me. I get
"Request is not authorized".
https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
Thanks,
Filip Kastl
Hello,
I think there was an error in bisecting these regressions. I can reproduce the same failure with commit 6dc6ca3302edadad7d4b195a05038995b84606d0, which happened before mine.
Thanks,
Slava
-----Original Message-----
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: Wednesday, May 21, 2025 9:10 PM
To: ohno.yasuyuki(a)fujitsu.com; itou.tetsuya(a)fujitsu.com; t-kawashima(a)fujitsu.com
Cc: Slava Zakharin <szakharin(a)nvidia.com>; maxim.kuvyrkov(a)linaro.org
Subject: [Linaro-TCWG-CI] llvmorg-21-init-11733-g2d12d31f44ac: 3 regressions 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-Ofast-sve_vls-lto-lld, after:
| commit llvmorg-21-init-11733-g2d12d31f44ac
| Author: Slava Zakharin <szakharin(a)nvidia.com>
| Date: Mon May 12 18:33:47 2025 -0700
|
| [flang] Propagate contiguous attribute through HLFIR. (#138797)
|
| This change allows marking more designators producing an opaque
| box with 'contiguous' attribute, e.g. like in test1 case
| in flang/test/HLFIR/propagate-contiguous-attribute.fir.
| ... 5 lines of the commit log omitted.
Produces 3 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0105 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0105/Fujitsu-Fortran-0105_0089.test
| NOEXE: test-suite :: Fujitsu/Fortran/0105/Fujitsu-Fortran-0105_0204.test
| NOEXE: test-suite :: Fujitsu/Fortran/0105/Fujitsu-Fortran-0105_0205.test
| # "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 -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-1686. 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/2d12d31f44acac54d7b2858624cb8a1…
Hi,
This regression is caused by a latent bug in the loop-interchange.
I've confirmed https://github.com/llvm/llvm-project/pull/140709 fixes the bug.
We'll wait for merge of https://github.com/llvm/llvm-project/pull/140709.
You don't need to investigate this failure.
Thanks.
> 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-21-init-12714-gd36028120a6e
> | Author: Sebastian Pop <spop(a)nvidia.com>
> | Date: Wed May 21 08:27:39 2025 -0500
> |
> | [flang] add -floop-interchange and enable it with opt levels (#140182)
> |
> | Enable the use of -floop-interchange from the flang driver.
> | Enable in flang LLVM's loop interchange at levels -O2, -O3, -Ofast, and -Os.
>
> Produces 1 regression:
> |
> | regressions.sum:
> | Running test-suite:Fujitsu/Fortran/0347 ...
> | FAIL: test-suite :: Fujitsu/Fortran/0347/Fujitsu-Fortran-0347_0240.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=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 "$\WORKSPACE/test/test-suite"
>
> We track this bug report under https://linaro.atlassian.net/browse/LLVM-1687. 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://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
>
> Full commit : https://github.com/llvm/llvm-project/commit/d36028120a6ef6346bfaafe82d4d1a2…