- linaro-toolchain - lists.linaro.org

by Paul Richard Thomas

The commit causing this regression was reverted three days later with r16-4111-g25f7f04e447dc0d2ed4c392eb21765e9ae9067d1 . Regards Paul

10 months, 2 weeks

2
1
0 0

How the NI CLAD Certification Boosts Your Career in Engineering and Automation

by David Gibbs

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

10 months, 2 weeks

1
0
0 0

Fwd: ☠ Buildbot (LLVM Buildbot): flang-arm64-windows-msvc - failed build (failure) (main)

by Mehdi AMINI

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

10 months, 2 weeks

2
2
0 0

Re: [Linaro-TCWG-CI] v6.17.3-130-g86f364ee5842: Failure on aarch64

by Nathan Chancellor

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

10 months, 2 weeks

1
0
0 0

[Linaro-TCWG-CI] glibc-2.42.9000-284-g27effb3d50: 9 regressions on aarch64

by ci_notify＠linaro.org

Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In master-aarch64, after: | commit glibc-2.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…

10 months, 2 weeks

4
6
0 0

Re: [Linaro-TCWG-CI] gcc-16-4604-g8b9cd6490ce5: Failure on aarch64

by Sam James

This is now https://gcc.gnu.org/PR122456.

10 months, 2 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-22-init-12058-ge6af0a40acc6: 26 regressions on aarch64

by Parzyszek, Krzysztof

[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…

10 months, 2 weeks

1
0
0 0

How Business Analysts Drive Organizational Success and Innovation

by David Gibbs

Business analysts are the bridge between strategy and execution, turning data into decisions that drive organizational success and innovation. By gathering stakeholder requirements, analyzing processes, and prioritizing solutions, they reduce waste, improve customer experiences, and accelerate time-to-market. Their expertise in mapping workflows and identifying opportunities for automation enables teams to focus on high-impact work while minimizing risk. Leveraging structured methodologies and modern analytics, business analysts translate complex information into clear, actionable roadmaps. This fosters cross-functional collaboration, supports data-driven culture, and uncovers new revenue streams. When aligned with leadership, their insights guide product strategy, operational improvements, and digital transformation initiatives that keep organizations competitive. Preparing for certification strengthens these capabilities. The PeopleCert Business Analysis Exam Questions help candidates master core techniques, from requirements elicitation to stakeholder management, ensuring they can contribute measurable value from day one. Employers value certified analysts who demonstrate proficiency; practicing with PeopleCert Business Analysis Exam Questions signals readiness and commitment to continuous improvement. Why I choose Certboosters: it offers focused practice tests, clear explanations, and realistic exam simulators tailored to real-world scenarios, making it easier to retain knowledge and build confidence before taking your exam. Start practicing today to accelerate your impact, career growth, and professional credibility. Use the link below to check the practice test questions: https://www.certboosters.com/peoplecert/path/peoplecert-business-analysis

10 months, 3 weeks

1
0
0 0

[Linaro-TCWG-CI] glibc-2.42.9000-337-g1b657c53c21: 4 regressions on arm

by ci_notify＠linaro.org

Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In glibc_check master-arm, after: | commit glibc-2.42.9000-337-g1b657c53c21 | Author: Siddhesh Poyarekar <siddhesh(a)sourceware.org> | Date: Fri Oct 10 20:21:13 2025 -0400 | | Simplify powl computation for small integral y [BZ #33411] | | The powl implementation for x86_64 ends up multiplying X once more than | necessary and then throwing away that result. This results in an | overflow flag being set in cases where there is no overflow. | ... 7 lines of the commit log omitted. Produces 4 regressions: | | regressions.sum: | Running glibc:math ... | FAIL: math/test-double-pow | FAIL: math/test-float32x-pow | FAIL: math/test-float64-pow | FAIL: math/test-ldouble-pow Used configuration : *CI config* tcwg_glibc_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-1714. 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_glibc_check--master-arm-build/3176/artifact/… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/3176/artifact/… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/3176/artifact/… Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/3176/artifact/… Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/3173/artifact/… 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=1b657c53c21a100082b0…

10 months, 3 weeks

1
0
0 0

[Linaro-TCWG-CI] glibc-2.42.9000-338-g324084649b2: Failure on arm

by ci_notify＠linaro.org

Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In master-arm, after: | commit glibc-2.42.9000-338-g324084649b2 | Author: DJ Delorie <dj(a)redhat.com> | Date: Wed Oct 15 21:37:56 2025 -0400 | | sprof: check pread size and offset for overflow | | Add a bit of descriptive paranoia to the values we read from | the ELF headers and use to access data. | | ... 1 lines of the commit log omitted. Produces Failure: | Results changed to | # reset_artifacts: | -10 | # true: | 0 | # build_abe binutils: | 1 | # build_abe gcc: | 2 | # build_abe linux: | 4 | # build_abe glibc: | # FAILED | # build_abe gdb: | # First few build errors in logs: | # 00:03:33 sprof.c:573:16: error: format ‘%zd’ expects argument of type ‘signed size_t’, but argument 5 has type ‘off_t’ {aka ‘long long int’} [-Werror=format=] | # 00:03:33 sprof.c:573:16: error: format ‘%zu’ expects argument of type ‘size_t’, but argument 6 has type ‘__off64_t’ {aka ‘long long int’} [-Werror=format=] | # 00:03:33 sprof.c:573:16: error: format ‘%zd’ expects argument of type ‘signed size_t’, but argument 5 has type ‘off_t’ {aka ‘long long int’} [-Werror=format=] | # 00:03:33 sprof.c:573:16: error: format ‘%zu’ expects argument of type ‘size_t’, but argument 6 has type ‘__off64_t’ {aka ‘long long int’} [-Werror=format=] | # 00:03:33 sprof.c:573:16: error: format ‘%zd’ expects argument of type ‘signed size_t’, but argument 5 has type ‘off_t’ {aka ‘long long int’} [-Werror=format=] | # 00:03:33 sprof.c:573:16: error: format ‘%zu’ expects argument of type ‘size_t’, but argument 6 has type ‘__off64_t’ {aka ‘long long int’} [-Werror=format=] | # 00:03:33 sprof.c:573:16: error: format ‘%zd’ expects argument of type ‘signed size_t’, but argument 5 has type ‘off_t’ {aka ‘long long int’} [-Werror=format=] | # 00:03:33 sprof.c:573:16: error: format ‘%zu’ expects argument of type ‘size_t’, but argument 6 has type ‘__off64_t’ {aka ‘long long int’} [-Werror=format=] | # 00:03:33 sprof.c:573:16: error: format ‘%zd’ expects argument of type ‘signed size_t’, but argument 5 has type ‘off_t’ {aka ‘long long int’} [-Werror=format=] | # 00:03:33 sprof.c:573:16: error: format ‘%zu’ expects argument of type ‘size_t’, but argument 6 has type ‘__off64_t’ {aka ‘long long int’} [-Werror=format=] | | From | # reset_artifacts: | -10 | # true: | 0 | # build_abe binutils: | 1 | # build_abe gcc: | 2 | # build_abe linux: | 4 | # build_abe glibc: | 5 | # build_abe gdb: | 6 Used configuration : *CI config* tcwg_gnu_native_build 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-1709. Please let us know if you have a fix. If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in * https://ci.linaro.org/job/tcwg_gnu_native_build--master-arm-build/1226/arti… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_gnu_native_build--master-arm-build/1226/arti… Current build : https://ci.linaro.org/job/tcwg_gnu_native_build--master-arm-build/1226/arti… Reference build : https://ci.linaro.org/job/tcwg_gnu_native_build--master-arm-build/1225/arti… 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=324084649b2da2f6840e…

10 months, 3 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-22-init-11449-ga6181dc84b79: 3 regressions on aarch64

by Takahiro Kawashima (Fujitsu)

Hi, These errors are probably 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-11449-ga6181dc84b79 > | Author: Peter Klausler <pklausler(a)nvidia.com> > | Date: Thu Oct 16 12:20:53 2025 -0700 > | > | [flang] Refine checks for NULL() in expressions (#163655) > | > | Fix a false positive "NULL can't be an operand here" error message > | arising in a defined generic interface for an intrinsic operator (==) > | with multiple spellings. > | ... 2 lines of the commit log omitted. > > Produces 3 regressions: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0573 ... > | NOEXE: test-suite :: Fujitsu/Fortran/0573/Fujitsu-Fortran-0573_0001.test > | NOEXE: test-suite :: Fujitsu/Fortran/0573/Fujitsu-Fortran-0573_0002.test > | NOEXE: test-suite :: Fujitsu/Fortran/0573/Fujitsu-Fortran-0573_0009.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=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-2097. 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/a6181dc84b79dd368c7a43ef4f6f164…

10 months, 3 weeks

1
0
0 0

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

11 months, 4 weeks

2
2
0 0

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.

11 months, 4 weeks

2
2
0 0

[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…

11 months, 4 weeks

3
2
0 0

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…

12 months

1
0
0 0

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

12 months

1
0
0 0

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

12 months

2
2
0 0

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 year

2
1
0 0

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 year

1
0
0 0

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…

1 year

1
0
0 0

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…

1 year

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-22-init-5156-g8849750e9988: 1 regression 1 fix on aarch64

by Takahiro Kawashima (Fujitsu)

Hi, This commit is practically a revert commit. This commit should not be harmful. Our team will take a look. Please ignore the mail. 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-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays, after: > | commit llvmorg-22-init-5156-g8849750e9988 > | Author: Nikita Popov <npopov(a)redhat.com> > | Date: Tue Aug 26 09:14:21 2025 +0200 > | > | [flang] Disable loop interchange by default (#155279) > | > | Disable loop interchange by default, while keeping the ability to > | explicitly enable using `-floop-interchange`. This matches Clang. > | > | ... 1 lines of the commit log omitted. > > Produces 1 regression 1 fix: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0631 ... > | FAIL: test-suite :: Fujitsu/Fortran/0631/Fujitsu-Fortran-0631_0058.test > | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one > | > | fixes.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;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 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG -fstack-arrays" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" > > We track this bug report under https://linaro.atlassian.net/browse/LLVM-1756. Please let us know if you have a fix. > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_… > > Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ > > Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_… > Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_… > > Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/… > > Full commit : https://github.com/llvm/llvm-project/commit/8849750e998819903dc749411bc9a7c…

1 year

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-22-init-4761-g6560adb58405: 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. 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-22-init-4761-g6560adb58405 > | Author: Connector Switch <c8ef(a)outlook.com> > | Date: Fri Aug 22 15:55:46 2025 +0800 > | > | [flang] optimize atand/atan2d precision (#154544) > | > | Part of https://github.com/llvm/llvm-project/issues/150452. > > Produces 1 regression: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0360 ... > | FAIL: test-suite :: Fujitsu/Fortran/0360/Fujitsu-Fortran-0360_0271.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 -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 -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite" > > We track this bug report under https://linaro.atlassian.net/browse/LLVM-1752. 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/6560adb5840596afbeb3f4574bf6d0c…

1 year

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-3301-g724d88900b7: Failure on arm

by Sam James

See PR121618. Should be fixed now.

1 year

1
0
0 0

[PATCH] [arm] require armv7 support for [PR120424] (was: Re: [PATCH, FYI?] [arm] [vxworks] require thumb2 for pr120424.C)

by Alexandre Oliva

On Jun 19, 2025, Alexandre Oliva <oliva(a)adacore.com> wrote: > Or maybe the requirements for this testcase should be stated as > arm_arch_v7? I'd have to add arm_arch_v7 to > check_effective_target_arm_arch_FUNC_ok et al, if there aren't reasons > why it's not there, but I'd be happy to do that, and use dg-add-options > instead of an explicit -march=armv7, like pr117675.c, if that would be > preferred. It turned out that the regression report I got from linaro was related https://linaro.atlassian.net/browse/GNU-1599 While testing a configuration with -mfloat-abi=hard, -marmv7 is rejected because it doesn't have an FPU. Requiring thumb2 wouldn't have avoided this failure, but requiring armv7 is a proper fix for both problems. (sorry it me took so long; I'm still busy busy with other fp2sp-elimination-disabled-during-lra problems affecting arm) Without stating the architecture version required by the test, test runs with options that are incompatible with the required architecture version fail, e.g. -mfloat-abi=hard. armv7 was not covered by the long list of arm variants in target-supports.exp, so add it, and use it for the effective target requirement and for the option. Tested on arm-eabi, and also on arm-vx7r2 with gcc-14. Ok to install? for gcc/testsuite/ChangeLog PR rtl-optimization/120424 * lib/target-supports.exp (arm arches): Add arm_arch_v7. * g++.target/arm/pr120424.C: Require armv7 support. Use dg-add-options arm_arch_v7 instead of explicit -march=armv7. --- gcc/testsuite/g++.target/arm/pr120424.C | 4 +++- gcc/testsuite/lib/target-supports.exp | 1 + 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/gcc/testsuite/g++.target/arm/pr120424.C b/gcc/testsuite/g++.target/arm/pr120424.C index 4d0e49013c04a..40295ac80da93 100644 --- a/gcc/testsuite/g++.target/arm/pr120424.C +++ b/gcc/testsuite/g++.target/arm/pr120424.C @@ -1,5 +1,7 @@ /* { dg-do compile } */ -/* { dg-options "-march=armv7 -O2 -fstack-clash-protection -fnon-call-exceptions" } */ +/* { dg-require-effective-target arm_arch_v7_ok } */ +/* { dg-options "-O2 -fstack-clash-protection -fnon-call-exceptions" } */ +/* { dg-add-options arm_arch_v7 } */ /* { dg-final { scan-assembler-not {#-8} } } */ /* LRA register elimination gets confused when register spilling causes arm_frame_pointer_required to switch from false to true, and diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp index dfffe3adfbdd0..858fa1787f19c 100644 --- a/gcc/testsuite/lib/target-supports.exp +++ b/gcc/testsuite/lib/target-supports.exp @@ -6073,6 +6073,7 @@ foreach { armfunc armflag armdefs } { v6z_arm "-march=armv6z+fp -marm" "__ARM_ARCH_6Z__ && !__thumb__" v6z_thumb "-march=armv6z+fp -mthumb -mfloat-abi=softfp" "__ARM_ARCH_6Z__ && __thumb__" v6m "-march=armv6-m -mthumb -mfloat-abi=soft" __ARM_ARCH_6M__ + v7 "-march=armv7" __ARM_ARCH_7__ v7a "-march=armv7-a+fp" __ARM_ARCH_7A__ v7a_arm "-march=armv7-a+fp -marm" "__ARM_ARCH_7A__ && !__thumb__" v7a_fp_hard "-march=armv7-a+fp -mfpu=auto -mfloat-abi=hard" __ARM_ARCH_7A__ -- Alexandre Oliva, happy hacker https://blog.lx.oliva.nom.br/ Free Software Activist FSFLA co-founder GNU Toolchain Engineer More tolerance and less prejudice are key for inclusion and diversity. Excluding neuro-others for not behaving ""normal"" is *not* inclusive!

1 year

2
2
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain