Hi Linaro folks!
It seems that the system running the armv8l has a pretty old pascal
compiler. I checked the log and it seems that, with that compiler
version, using fpc -g will generate stabs information, rather than DWARF
information.
So in one sense, these regressions are expected, but more importantly,
you should take a look at updating the armv8l machine so that pascal
tests can continue working
On 10/23/25 10:42 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 gdb_check master-arm, after:
> | commit gdb-17-branchpoint-577-gbaeb632f1b7
> | Author: Guinevere Larsen <guinevere(a)redhat.com>
> | Date: Wed Jan 22 14:05:01 2025 -0300
> |
> | gdb: Remove stabs support from ELF files
> |
> | This commit makes it so that GDB won't read stabs information from ELF
> | files. If stabs is detected in an ELF file, the reader now warns the user
> | that stabs is not supported.
> | ... 6 lines of the commit log omitted.
>
> Produces 118 regressions:
> |
> | regressions.sum:
> | Running gdb:gdb.pascal/case-insensitive-symbols.exp ...
> | FAIL: gdb.pascal/case-insensitive-symbols.exp: gdb_breakpoint: set breakpoint at case-insensitive-symbols.pas:43
> | Running gdb:gdb.pascal/floats.exp ...
> | FAIL: gdb.pascal/floats.exp: Going to second breakpoint (the program is no longer running)
> | FAIL: gdb.pascal/floats.exp: Test sin(pi) is equal to 0
> | ... and 119 more
>
> Used configuration :
> *CI config* tcwg_gdb_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-1715. 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_gdb_check--master-arm-build/3112/artifact/ar…
> 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-build/3112/artifact/ar…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/3112/artifact/ar…
>
> Current build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/3112/artifact/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/3111/artifact/ar…
>
> Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gdb/s…
>
> Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=baeb632f1b7ce…
--
Cheers,
Guinevere Larsen
It/she
On Tue, Oct 28, 2025 at 12:07 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 gcc_check master-aarch64, after:
> | commit gcc-16-4667-gdcf69bdcd49
> | Author: H.J. Lu <hjl.tools(a)gmail.com>
> | Date: Sun Oct 26 08:42:20 2025 +0800
> |
> | c: Try the type with the previous function attributes
> |
> | When there are 2 conflicting function declarations, try the new type
> | with the previous TYPE_ATTRIBUTES if the current declaration has no
> | TYPE_ATTRIBUTES to support
> | ... 44 lines of the commit log omitted.
>
> Produces 19 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.target/aarch64/sme/aarch64-sme.exp ...
> | FAIL: gcc.target/aarch64/sme/streaming_mode_1.c (test for errors, line 10)
> | FAIL: gcc.target/aarch64/sme/streaming_mode_1.c (test for errors, line 121)
> | FAIL: gcc.target/aarch64/sme/streaming_mode_1.c (test for errors, line 16)
> | FAIL: gcc.target/aarch64/sme/streaming_mode_1.c (test for errors, line 30)
> | ... and 15 more
>
After
commit dcf69bdcd49bccd901bfb01db7c15530e9a70dc0
Author: H.J. Lu <hjl.tools(a)gmail.com>
Date: Sun Oct 26 08:42:20 2025 +0800
c: Try the type with the previous function attributes
gcc no longer issues an error for:
void sc_c () [[arm::streaming_compatible]];
void sc_c () {}
Instead, the previous type attributes are applied to the current function
definition. The resulting function definition is compatible with the
previous declaration.
PR c/122427
* gcc.target/aarch64/sme/streaming_mode_1.c: Remove dg-error.
--
H.J.
On Wed, 29 Oct 2025 at 22:04, <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-aarch64, after:
> | commit gcc-16-4709-gc55c1de3a9a
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Tue Oct 28 12:15:52 2025 +0000
> |
> | libstdc++: Simplify std::regex_traits::value
> |
> | We don't need to use an istringstream to convert a hex digit to its
> | numerical value. And if we don't use istringstream there, we don't need
> | to include <sstream> in <regex>.
> | ... 8 lines of the commit log omitted.
>
> Produces 3 regressions:
> |
> | regressions.sum:
> | Running g++:g++.dg/dg.exp ...
> | FAIL: g++.dg/warn/uninit-pr105562.C -std=gnu++11 (test for excess errors)
> | FAIL: g++.dg/warn/uninit-pr105562.C -std=gnu++17 (test for excess errors)
> | FAIL: g++.dg/warn/uninit-pr105562.C -std=gnu++26 (test for excess errors)
>
> Used configuration :
> *CI config* tcwg_gcc_check 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-1735. 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.
Fixed at r16-4714-gcc78f8523832d6
>
> -----------------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-aarch64-build/4300/artifac…
> 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-aarch64-build/4300/artifac…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/4300/artifac…
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/4300/artifac…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/4299/artifac…
>
> 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
Earning the NI Certified LabVIEW Associate Developer (CLAD) certification is a practical step for engineers and automation professionals aiming to prove hands-on LabVIEW competence. Employers value the problem-solving and system-design skills demonstrated by candidates who pass NI Certified LabVIEW Associate Developer CLAD Exam Questions, because the credential signals consistent coding practices and real-world application ability.
The CLAD credential accelerates career growth by opening roles in test engineering, instrumentation, robotics, and industrial automation. With a firm foundation in graphical programming, certified professionals can contribute to project efficiency, reduce development time, and improve system reliability. Preparing with focused resources for NI Certified LabVIEW Associate Developer CLAD Exam Questions helps candidates master core topics such as dataflow, debugging, and modular design—skills directly transferable to workplace challenges.
I selected Certboosters because it provides structured study plans, realistic practice tests, and expert feedback to increase confidence and exam readiness; their materials are tailored to practical outcomes and mirror exam style while reinforcing applied LabVIEW techniques.
In short, the NI CLAD certification strengthens résumés, accelerates promotions, and equips engineers with an industry-recognized proof of LabVIEW proficiency that employers seek in automation and control-system roles.
Use the link below to check the practice test questions: https://www.certboosters.com/ni/path/clad
Hi folks,
I have a strong suspicion that this bot has an incremental build issue
right now.
Can someone trigger a clean build please?
Thanks!
Mehdi
---------- Forwarded message ---------
From: <llvm.buildmaster(a)lab.llvm.org>
Date: Tue, Oct 28, 2025 at 12:51 AM
Subject: ☠ Buildbot (LLVM Buildbot): flang-arm64-windows-msvc - failed
build (failure) (main)
To: Mehdi Amini <joker.eph(a)gmail.com>
Cc: <llvm.buildmaster(a)lab.llvm.org>
The Buildbot has detected a new failure on builder flang-arm64-windows-msvc
while building flang,mlir.
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/207/builds/9096
Worker for this Build: linaro-armv8-windows-msvc-01
Blamelist:
Mehdi Amini <joker.eph(a)gmail.com>
BUILD FAILED: failed build (failure)
Step 5 (build-unified-tree) failure: build (failure)
...
359 | return {APFloat(*smt, value.real()), APFloat(*smt,
value.imag())};
| ^
c:\Program Files\Microsoft Visual
Studio\2022\Community\VC\Tools\MSVC\14.39.33519\include\complex(1315,5):
note: 'complex' has been explicitly marked deprecated here
1315 | _DEPRECATE_NONFLOATING_COMPLEX
| ^
c:\Program Files\Microsoft Visual
Studio\2022\Community\VC\Tools\MSVC\14.39.33519\include\yvals_core.h(1450,7):
note: expanded from macro '_DEPRECATE_NONFLOATING_COMPLEX'
1450 | [[deprecated("warning STL4037: "
\
| ^
1 warning generated.
84.583 [1719/10/276] Building CXX object
tools/mlir/lib/Dialect/MemRef/IR/CMakeFiles/obj.MLIRMemRefDialect.dir/MemRefDialect.cpp.obj
FAILED:
tools/mlir/lib/Dialect/MemRef/IR/CMakeFiles/obj.MLIRMemRefDialect.dir/MemRefDialect.cpp.obj
C:\Users\tcwg\scoop\shims\ccache.exe
C:\Users\tcwg\scoop\apps\llvm-arm64\current\bin\clang-cl.exe /nologo -TP
-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/mlir/lib/Dialect/MemRef/IR
-IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/lib/Dialect/MemRef/IR
-IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/mlir/include
-IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/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
/DWIN32 /D_WINDOWS /Zc:inline /Zc:__cplusplus /Oi /Brepro /bigobj
/permissive- -Werr
or=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 -Wno-pass-failed -Wmisleading-indentation
-Wctad-maybe-unsupported /Gw -Wundef -Werror=mismatched-tags
-Werror=global-constructors /O2 /Ob2 -std:c++17 -MD /EHs-c- /GR- -UNDEBUG
/showIncludes
/Fotools/mlir/lib/Dialect/MemRef/IR/CMakeFiles/obj.MLIRMemRefDialect.dir/MemRefDialect.cpp.obj
/Fdtools\mlir\lib\Dialect\MemRef\IR\CMakeFiles\obj.MLIRMemRefDialect.dir\
-c --
C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/lib/Dialect/MemRef/IR/MemRefDialect.cpp
In file included from
C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/lib/Dialect/MemRef/IR/MemRefDialect.cpp:9:
In file included from
C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include\mlir/Conversion/ConvertToEmitC/ToEmitCInterface.h:14:
In file included from
C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include\mlir/IR/OpDefinition.h:22:
In file included from
C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include\mlir/IR/Dialect.h:17:
In file included from
C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include\mlir/IR/OperationSupport.h:19:
C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include\mlir/IR/BuiltinAttributes.h(359,14):
warning: 'complex' is deprecated: warning STL4037: The effect of
instantiating the template std::complex for any type other than float,
double, or long double is unspecified. You can define
_SILENCE_NONFLOATING_COMPLEX_DEPRECATION_WARNING to suppress this warning.
[-Wdeprecated-declarations]
359 | return {APFloat(*smt, value.real()), APFloat(*smt,
value.imag())};
| ^
c:\Program Files\Microsoft Visual
Studio\2022\Community\VC\Tools\MSVC\14.39.33519\include\complex(1315,5):
note: 'complex' has been explicitly marked deprecated here
1315 | _DEPRECATE_NONFLOATING_COMPLEX
| ^
c:\Program Files\Microsoft Visual
Studio\2022\Community\VC\Tools\MSVC\14.39.33519\include\yvals_core.h(1450,7):
note: expanded from macro '_DEPRECATE_NONFLOATING_COMPLEX'
1450 | [[deprecated("warning STL4037: "
\
| ^
In file included from
C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/lib/Dialect/MemRef/IR/MemRefDialect.cpp:12:
In file included from
C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include\mlir/Dialect/MemRef/IR/MemRef.h:13:
In file included from
C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include\mlir/Dialect/Arith/IR/Arith.h:17:
In file included from
C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include\mlir/Interfaces/ControlFlowInterfaces.h:371:
C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/mlir/include\mlir/Interfaces/ControlFlowInterfaces.h.inc(1118,84):
error: no viable conversion from '::mlir::RegionSuccessor' to
'::mlir::RegionBranchPoint'
1118 | return
(llvm::cast<ConcreteOp>(tablegen_opaque_val)).getMutableSuccessorOperands(point);
|
^~~~~
C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/mlir/include\mlir/Interfaces/ControlFlowInterfaces.h.inc(435,23):
note: in instantiation of member function
'mlir::detail::RegionBranchTerminatorOpInterfaceInterfaceTraits::Model<mlir::memref::AtomicYieldOp>::getMutableSuccessorOperands'
requested here
435 | Model() : Concept{getMutableSuccessorOperands,
getSuccessorRegions} {}
| ^
C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include\mlir/Support/InterfaceSupport.h(238,46):
note: in instantiation of member function
'mlir::detail::RegionBranchTerminatorOpInterfaceInterfaceTraits::Model<mlir::memref::AtomicYieldOp>::Model'
requested here
238 | new (malloc(sizeof(InterfaceModel))) InterfaceModel();
| ^
C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include\mlir/Support/InterfaceSupport.h(225,7):
note: in instantiation of function template specialization
'mlir::detail::InterfaceMap::insertModel<mlir::detail::RegionBranchTerminatorOpInterfaceInterfaceTraits::Model<mlir::memref::AtomicYieldOp>>'
requested here
225 | insertModel<typename T::ModelT>();
| ^
C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include\mlir/Support/InterfaceSupport.h(199,10):
note: in instantiation of function template specialization
'mlir::detail::InterfaceMap::insertPotentialInterface<mlir::RegionBranchTerminatorOpInterface::Trait<mlir::memref::AtomicYieldOp>>'
requested here
199 | (map.insertPotentialInterface<Types>(), ...);
| ^
C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include\mlir/IR/OpDefinition.h(1877,43):
note: in instantiation of function template specialization
'mlir::detail::InterfaceMap::get<mlir::OpTrait::ZeroRegions<mlir::memref::AtomicYieldOp>,
mlir::OpTrait::ZeroResults<mlir::memref::AtomicYieldOp>,
mlir::OpTrait::ZeroSuccessors<mlir::memref::AtomicYieldOp>,
mlir::OpTrait::OneOperand<mlir::memref::AtomicYieldOp>,
mlir::OpTrait::HasParent<mlir::memref::GenericAtomicRMWOp>::Impl<mlir::memref::AtomicYieldOp>,
mlir::OpTrait::OpInvariants<mlir::memref::AtomicYieldOp>,
mlir::ConditionallySpeculatable::Trait<mlir::memref::AtomicYieldOp>,
mlir::OpTrait::AlwaysSpeculatableImplTrait<mlir::memref::AtomicYieldOp>,
mlir::MemoryEffectOpInterface::Trait<mlir::memref::AtomicYieldOp>,
mlir::OpTrait::IsTerminator<mlir::memref::AtomicYieldOp>,
mlir::RegionBranchTerminatorOpInterface::Trait<mlir::memref::AtomicYieldOp>,
mlir::OpTrait::ReturnLike<mlir::memref::AtomicYieldOp>>' requested he
re
1877 | return detail::InterfaceMap::template
get<Traits<ConcreteType>...>();
| ^
C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include\mlir/IR/OperationSupport.h(533,55):
note: in instantiation of member function
'mlir::Op<mlir::memref::AtomicYieldOp, mlir::OpTrait::ZeroRegions,
mlir::OpTrait::ZeroResults, mlir::OpTrait::ZeroSuccessors,
mlir::OpTrait::OneOperand,
mlir::OpTrait::HasParent<mlir::memref::GenericAtomicRMWOp>::Impl,
mlir::OpTrait::OpInvariants, mlir::ConditionallySpeculatable::Trait,
mlir::OpTrait::AlwaysSpeculatableImplTrait,
mlir::MemoryEffectOpInterface::Trait, mlir::OpTrait::IsTerminator,
mlir::RegionBranchTerminatorOpInterface::Trait,
mlir::OpTrait::ReturnLike>::getInterfaceMap' requested here
Sincerely,
LLVM Buildbot
On Sun, Oct 26, 2025 at 05:01:16PM +0000, ci_notify(a)linaro.org wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In tcwg_kernel/llvm-master-aarch64-stable-allnoconfig, after:
> | commit v6.17.3-130-g86f364ee5842
> | Author: Masahiro Yamada <masahiroy(a)kernel.org>
> | Date: Thu Sep 18 10:05:46 2025 +0200
> |
> | kbuild: always create intermediate vmlinux.unstripped
> |
> | [ Upstream commit 0ce5139fd96e9d415d3faaef1c575e238f9bbd67 ]
> |
> | Generate the intermediate vmlinux.unstripped regardless of
> | ... 14 lines of the commit log omitted.
This is reproducible for me locally with:
$ make -skj"$(nproc)" ARCH=arm64 CC=clang CROSS_COMPILE=aarch64-linux-gnu- HOSTCC=clang LD=ld.lld clean allnoconfig all
aarch64-linux-gnu-objcopy: vmlinux: file format not recognized
...
This does not occur with llvm-objcopy via LLVM=1 nor does it happen with
an all GNU setup. This feels like a bug in GNU objcopy though, as this
is reproducible with:
$ aarch64-linux-gnu-objcopy --set-section-flags .modinfo=noload vmlinux.unstripped vmlinux.objcopy
$ file vmlinux.unstripped vmlinux.objcopy
vmlinux.unstripped: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), statically linked, BuildID[sha1]=18512f67dae70a7fae145b34514054a8b8b3c105, not stripped
vmlinux.objcopy: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), statically linked, BuildID[sha1]=18512f67dae70a7fae145b34514054a8b8b3c105, not stripped
$ aarch64-linux-gnu-objcopy --remove-section=.modinfo -w --strip-unneeded-symbol='__mod_device_table__*' vmlinux.objcopy
aarch64-linux-gnu-objcopy: vmlinux.objcopy: file format not recognized
$ aarch64-linux-gnu-objcopy --version | head -1
GNU objcopy (GNU Binutils) 2.45.50.20251028
Cheers,
Nathan
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.42.9000-284-g27effb3d50
| Author: Yury Khrustalev <yury.khrustalev(a)arm.com>
| Date: Thu Sep 25 15:54:36 2025 +0100
|
| aarch64: clear ZA state of SME before clone and clone3 syscalls
|
| This change adds a call to the __arm_za_disable() function immediately
| before the SVC instruction inside clone() and clone3() wrappers. It also
| adds a macro for inline clone() used in fork() and adds the same call to
| ... 129 lines of the commit log omitted.
Produces 9 regressions:
|
| regressions.sum:
| Running gdb:gdb.threads/foll-fork-other-thread.exp ...
| FAIL: gdb.threads/foll-fork-other-thread.exp: fork_func=fork: follow=child: target-non-stop=auto: non-stop=off: displaced-stepping=auto: bt
| FAIL: gdb.threads/foll-fork-other-thread.exp: fork_func=fork: follow=child: target-non-stop=auto: non-stop=off: displaced-stepping=off: bt
| FAIL: gdb.threads/foll-fork-other-thread.exp: fork_func=fork: follow=child: target-non-stop=auto: non-stop=off: displaced-stepping=on: bt
| FAIL: gdb.threads/foll-fork-other-thread.exp: fork_func=fork: follow=child: target-non-stop=off: non-stop=off: displaced-stepping=auto: bt
| ... and 5 more
Used configuration :
*CI config* tcwg_gnu_native_check_gdb 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-1706. 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-aarch64-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_native_check_gdb--master-aarch64-build/1…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1…
Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1…
Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/glibc…
Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=27effb3d50424fb9634b…
[AMD Official Use Only - AMD Internal Distribution Only]
Hi,
I put out a PR with the fix: https://github.com/llvm/llvm-project/pull/165250
Sorry about the breakage.
-Krzysztof
________________________________
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: Saturday, October 25, 2025 8:51 AM
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: Parzyszek, Krzysztof <Krzysztof.Parzyszek(a)amd.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>
Subject: [Linaro-TCWG-CI] llvmorg-22-init-12058-ge6af0a40acc6: 26 regressions on aarch64
Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
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-12058-ge6af0a40acc6
| Author: Krzysztof Parzyszek <Krzysztof.Parzyszek(a)amd.com>
| Date: Wed Oct 22 11:46:11 2025 -0500
|
| [flang][OpenMP] Keep track of scoping units in OmpStructureChecker (#164419)
|
| Introduce a stack of scopes to OmpStructureChecker for scoping units,
| plus function/subroutine entries in interfaces.
|
| ... 3 lines of the commit log omitted.
Produces 26 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0156 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0156/Fujitsu-Fortran-0156_0011.test
| Running test-suite:Fujitsu/Fortran/0391 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0391/Fujitsu-Fortran-0391_0023.test
| Running test-suite:Fujitsu/Fortran/0401 ...
| ... and 32 more
| # "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=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-2106. 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/e6af0a40acc6d244b6862142829274e…