- linaro-toolchain - lists.linaro.org

Norwegian Air Flight Cancellation: A Quick and Simple Guide

by 8cf5i6jjvy＠bltiwd.com

If you need to cancel your Norwegian Air flight, do not worry — the process is f Airly straightforward! You can call Norwegian Air directly at 📞 1-866-284-3022. Whether you are canceling due to personal reasons, weather disruptions, or a change in plans, this guide will walk you through every step. While cancellations can be made online, calling may provide faster support and more detailed assistance. 📍 Step 1: Find Your Flight Information Before you call or go online, make sure you have the following information ready: ✅ Your booking confirmation number ✅ The name on the reservation ✅ Your flight details (departure date, destination, etc.) Having this information handy will make the process quicker, especially if you are speaking with a Norwegian Air representative at 📞 1-866-284-3022. 📞 Step 2: Call Norwegian Air Customer Support The easiest and most direct way to cancel your flight is by calling Norwegian Air customer service at 1-866-284-3022. This line is available to assist with cancellations, modifications, and refund requests. 🧑‍💼 When you call: You will be prompted to enter your confirmation number Select the option for "existing reservation" Ask to speak to a live representative if needed Pro tip: Call during off-peak hours (early mornings or late evenings) to avoid long wait times. 🌐 Step 3: Cancel Online (Alternative Option) If you prefer to cancel online, follow these steps: Go to the official Norwegian Air website Click on "My Trips" at the top of the homepage Enter your last name and confirmation code Find the reservation you want to cancel Click on “Cancel” and follow the on-screen instructions However, if you run into any issues or if your fare type does not allow online cancellations, don’t hesitate to call 1-866-284-3022 for support. 💸 Step 4: Check for Refund or Credit Eligibility Norwegian Air is a low-cost carrier, and refund policies can vary depending on the fare type. Here is a quick breakdown: 🟢 WORKS Bundle or Refundable Tickets: Eligible for a full refund 🟡 Standard Tickets: May not be refundable but can be canceled for a credit (valid for 90 days) 🔴 Basic Fare or Promo Tickets: Often non-refundable To clarify your eligibility, it is best to speak to a Vietnam representative directly at 📞 1-866-284-3022. They can explain whether you will receive a refund, a travel credit, or incur a cancellation fee. ⏱️ Step 5: Cancel Within 24 Hours (If Possible) ✅ If you booked your ticket less than 24 hours ago AND your flight is at least 7 days away, you are eligible for a full refund with no cancellation fees. To take advantage of this policy, it is strongly advised to call 1-866-284-3022 right away and notify them that you fall within the 24-hour window. 📧 Step 6: Get Confirmation of Cancellation Once your flight is canceled, make sure to: 📨 Check your email for a cancellation confirmation 💳 Verify if any refund or credit has been issued to your account 📅 Note the expiration date of any travel credit issued (typically valid for 90 days) If you have not received confirmation within a few hours, call 📞 1-866-284-3022 again to follow up and ensure your cancellation was processed correctly. 🤔 Need Help? Contact Norwegian Air Again Vietnam’s website can sometimes be tricky or limited in functionality, especially for special fares or last-minute cancellations. That is why calling customer service at 📞 1-866-284-3022 is always the most reliable option. Their agents can also assist with: Modifying your travel dates Applying travel credits Rebooking future flights Answering policy-related questions ✍️ Final Thoughts Canceling a Norwegian Air flight does not have to be stressful. Whether you are canceling online or over the phone, knowing the process and your rights can save you time and money. Always keep the Vietnam customer service number 📞 1-866-284-3022 on hand for quick assistance and peace of mind. 🧭 Quick Recap: Prepare your booking info Try canceling online or via the Vietnam app For best results, call Vietnam directly at 📞 1-866-284-3022 Check your eligibility for refunds or travel credits Always get a cancellation confirmation ✈️ Safe travels — or smooth cancellations — whichever your journey brings next!

7 months, 3 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] v6.18-rc1-73-g3ffeb17a9a27a: Failure on aarch64

by Nathan Chancellor

On Sun, Nov 16, 2025 at 09:46:23AM +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-next-allmodconfig, after: > | commit v6.18-rc1-73-g3ffeb17a9a27a > | Author: Christian Marangi <ansuelsmth(a)gmail.com> > | Date: Fri Nov 7 00:57:08 2025 +0100 > | > | pinctrl: airoha: add support for Airoha AN7583 PINs > | > | Add all the required entry to add suppot for Airoha AN7583 PINs. > | > | Where possible the same function group are used from Airoha EN7581 to > | ... 4 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: > | 27020 > | # First few build errors in logs: > | # 00:37:42 drivers/pinctrl/mediatek/pinctrl-airoha.c:2064:41: error: variable 'an7583_pinctrl_drive_e2_conf' is not needed and will not be emitted [-Werror,-Wunneeded-internal-declaration] https://lore.kernel.org/20251112-pinctrl-airoha-fix-an7583-drive-e2-confg-u… Cheers, Nathan

7 months, 3 weeks

1
0
0 0

[Linaro-TCWG-CI] glibc-2.42.9000-426-g53807741fb4: 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 glibc_check master-arm, after: | commit glibc-2.42.9000-426-g53807741fb4 | Author: Wilco Dijkstra <Wilco.Dijkstra(a)arm.com> | Date: Thu Sep 11 10:49:47 2025 -0300 | | Define __HAVE_64B_ATOMICS from compiler support | | Now that atomic builtins are used by default, we can rely on the | compiler to define when to use 64-bit atomic operations. | | ... 7 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running glibc:nss ... | FAIL: nss/tst-cancel-getpwuid_r 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-1745. 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/3193/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/3193/artifact/… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/3193/artifact/… Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/3193/artifact/… Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/3192/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=53807741fb44edb8e7c0…

8 months

2
1
0 0

[Linaro-TCWG-CI] llvmorg-22-init-14086-g046ae8553606: Failure on aarch64

by ci_notify＠linaro.org

Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In tcwg_flang_build/main-aarch64, after: | commit llvmorg-22-init-14086-g046ae8553606 | Author: Christopher Ferris <cferris1000(a)users.noreply.github.com> | Date: Mon Nov 10 14:17:23 2025 -0800 | | [scudo] Small cleanup of memory tagging code. (#166860) | | Make the systemSupportsMemoryTagging() function return even on system | that don't support memory tagging. This avoids the need to always check | if memory tagging is supported before calling th function. | ... 5 lines of the commit log omitted. Produces Failure: | Results changed to | # reset_artifacts: | -10 | # true: | 0 | # build_llvm -- clang;lld;flang;clang-tools-extra openmp : | # FAILED | # First few build errors in logs: | # 00:10:20 ld.lld: error: undefined symbol: __cxa_guard_acquire | # 00:10:20 ld.lld: error: undefined symbol: __cxa_guard_release | # 00:10:20 clang++: error: linker command failed with exit code 1 (use -v to see invocation) | | From | # reset_artifacts: | -10 | # true: | 0 | # build_llvm -- clang;lld;flang;clang-tools-extra openmp : | 1 Used configuration : tcwg_flang_build/main-aarch64 We track this bug report under https://linaro.atlassian.net/browse/LLVM-2115. 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_flang_build--main-aarch64-build/6073/artifac… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/6073/artifac… Current build : https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/6073/artifac… Reference build : https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/6070/artifac… 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/046ae855360614c5980d0ced0c55b5d…

8 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-4946-g22b3de712f7: Failure on arm

by Sam James

-> PR122575.

8 months, 1 week

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-5025-g0013501e462: 3 regressions on aarch64

by Siddhesh Poyarekar

On 2025-11-04 12:03, 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-5025-g0013501e462 > | Author: Siddhesh Poyarekar <siddhesh(a)gotplt.org> > | Date: Mon Nov 3 17:02:00 2025 -0600 > | > | lto/122515: Fix archive offset types for i686 > | > | On i686, offsets into object archives could be 64-bit, but they're > | inconsistently treated across the lto, which may sometimes result in > | truncation of those offsets for large archives. > | ... 36 lines of the commit log omitted. > > Produces 3 regressions: > | > | regressions.sum: > | Running gcc:gcc.dg/lto/lto.exp ... > | UNRESOLVED: gcc.dg/lto/pr122515 c_lto_pr122515_0.o-c_lto_pr122515.a execute -flto=auto -ffat-lto-objects > | UNRESOLVED: gcc.dg/lto/pr122515 c_lto_pr122515_0.o-c_lto_pr122515.a link -flto=auto -ffat-lto-objects > | FAIL: gcc.dg/lto/pr122515, ar returned 1: /WORKSPACE/abe/builds/destdir/aarch64-unknown-linux-gnu/bin/gcc-ar: Cannot find plugin 'liblto_plugin.so' > > 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-1744. Please let us know if you have a fix. > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/4333/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/4333/artifac… The Jenkins instance seems to be down. Is there another way to find out how this was configured? ISTM that liblto_plugin.so may not have been built. Sid

8 months, 1 week

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-22-init-12981-g2abcb19af225: 17 regressions on aarch64

by Peter Klausler

Those tests use a non-conforming and non-portable feature that flang-new now flags as a compilation error. Please disable them. From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Date: Monday, November 3, 2025 at 06:30 To: ohno.yasuyuki(a)fujitsu.com <ohno.yasuyuki(a)fujitsu.com>, itou.tetsuya(a)fujitsu.com <itou.tetsuya(a)fujitsu.com>, t-kawashima(a)fujitsu.com <t-kawashima(a)fujitsu.com> Cc: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>, Peter Klausler <pklausler(a)nvidia.com> Subject: [Linaro-TCWG-CI] llvmorg-22-init-12981-g2abcb19af225: 17 regressions on aarch64 External email: Use caution opening links or attachments Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In tcwg_flang_test/main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays, after: | commit llvmorg-22-init-12981-g2abcb19af225 | Author: Peter Klausler <pklausler(a)nvidia.com> | Date: Fri Oct 31 10:27:30 2025 -0700 | | [flang] Don't allow function calls to PROCEDURE() (#165786) | | PROCEDURE() declares a procedure with no interface or result type. (When | used to declare a derived type component, it must also be a NOPASS | POINTER.) Document that we allow such procedures to be called as | ... 7 lines of the commit log omitted. Produces 17 regressions: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0383 ... | NOEXE: test-suite :: Fujitsu/Fortran/0383/Fujitsu-Fortran-0383_0026.test | NOEXE: test-suite :: Fujitsu/Fortran/0383/Fujitsu-Fortran-0383_0027.test | Running test-suite:Fujitsu/Fortran/0387 ... | NOEXE: test-suite :: Fujitsu/Fortran/0387/Fujitsu-Fortran-0387_0058.test | ... and 22 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 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -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 -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 -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG -fstack-arrays" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" We track this bug report under https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinaro.at…<https://linaro.atlassian.net/browse/LLVM-2112>. Please let us know if you have a fix. If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in *.log.1.xz files in * https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…> The full lists of regressions and improvements as well as configure and make commands are in * https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…> The list of [ignored] baseline and flaky failures are in * https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…> Fujitsu testsuite : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…<https://github.com/fujitsu/compiler-test-suite/> Current build : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…> Reference build : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…> Instruction to reproduce the build : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.co…<https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/…> Full commit : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…<https://github.com/llvm/llvm-project/commit/2abcb19af22518643c9ebeddb353c00…>

8 months, 1 week

1
0
0 0

Re: [Linaro-TCWG-CI] gdb-17-branchpoint-577-gbaeb632f1b7: 118 regressions on arm

by Guinevere Larsen

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

8 months, 2 weeks

2
1
0 0

[PATCH] aarch64: streaming_mode_1.c: Remove dg-error

by H.J. Lu

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.

8 months, 2 weeks

2
3
0 0

Re: [Linaro-TCWG-CI] gcc-16-4709-gc55c1de3a9a: 3 regressions on aarch64

by Jonathan Wakely

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

8 months, 2 weeks

1
0
0 0

gcc-16-4069-ge77daa57300

by Paul Richard Thomas

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

8 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

8 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

8 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

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

8 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.

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

8 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

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

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

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

8 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

9 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.

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

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

10 months

1
0
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain