linaro-toolchain November 2025

linaro-toolchain@lists.linaro.org

9 participants
11 discussions

[Linaro-TCWG-CI] glibc-2.42.9000-537-gcd748a63ab1: 5 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-537-gcd748a63ab1 | Author: Joseph Myers <josmyers(a)redhat.com> | Date: Thu Nov 20 19:30:27 2025 +0000 | | Implement C23 const-preserving standard library macros | | C23 makes various standard library functions, that return a pointer | into an input array, into macros that return a pointer to const when | the relevant argument passed to the macro is a pointer to const. (The | ... 35 lines of the commit log omitted. Produces 5 regressions: | | regressions.sum: | Running gcc:gcc.dg/analyzer/analyzer.exp ... | FAIL: gcc.dg/analyzer/strchr-1.c (test for warnings, line 32) | FAIL: gcc.dg/analyzer/strchr-1.c (test for warnings, line 39) | FAIL: gcc.dg/analyzer/strchr-1.c (test for excess errors) | FAIL: gcc.dg/analyzer/strchr-1.c event at line 33 (test for warnings, line 32) | ... and 1 more 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-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_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/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/glibc… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=cd748a63ab1a7ae84617…

7 hours, 18 minutes

Re: [Linaro-TCWG-CI] glibc-2.42.9000-514-g8d999a69936: 2 regressions on arm

by H. Peter Anvin

On 2025-11-19 04:31, ci_notify(a)linaro.org wrote: > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In master-arm, after: > | commit glibc-2.42.9000-514-g8d999a69936 > | Author: H. Peter Anvin <hpa(a)zytor.com> > | Date: Mon Oct 20 13:42:09 2025 -0700 > | > | linux/termios: clear k_termios.c_cflag & CIBAUD for non-split speed [BZ 33340] > | > | After getting more experience with the various broken direct-to-ioctl > | termios2 hacks using Fedora 43 beta, I have found a fair number of > | cases where the software would fail to set, or clear CIBAUD for > | ... 29 lines of the commit log omitte > > Produces 2 regressions: > | > | regressions.sum: > | Running gdb:gdb.base/term.exp ... > | FAIL: gdb.base/term.exp: after last resume: info terminal > | FAIL: gdb.base/term.exp: post tcsetattr: info terminal > > Used configuration : > *CI config* tcwg_gnu_native_check_gdb 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-1753. Please let us know if you have a fix. > I have root caused this test failure to the script assuming that tcgetattr() ... tcsetattr() ... tcgetattr() will always produce a configuration that is bitwise identical to the previous configuration, which is not true with normalization. This is an invalid use of the termios structure, which is mostly an opaque data type, but gdb has a rather unique use case here in that it is a debugger, and as such "it is not bitwise identical but has the same function" might still be a problem for them. Either way, this I believe is something that needs to be addressed in gdb; either by using the kernel interface directly for the purpose of saving and restoring, alternatively they may need some assistance in the form of a dedicated save/restore interface. I have filed this bug in the gdb bugzilla to address this issue: https://sourceware.org/bugzilla/show_bug.cgi?id=33652 -hpa

1 day, 15 hours

Re: [Linaro-TCWG-CI] glibc-2.42.9000-514-g8d999a69936: 2 regressions on arm

by H. Peter Anvin

This is a false positive, as the test is invalid: it expects the sequence tcgetattr ... tcsetattr ... tcgetattr to produce a bitwise identical termios structure, and that is simply not a valid assumption for *multiple* reasons. -hpa On 2025-11-19 04:31, ci_notify(a)linaro.org wrote: > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In master-arm, after: > | commit glibc-2.42.9000-514-g8d999a69936 > | Author: H. Peter Anvin <hpa(a)zytor.com> > | Date: Mon Oct 20 13:42:09 2025 -0700 > | > | linux/termios: clear k_termios.c_cflag & CIBAUD for non-split speed [BZ 33340] > | > | After getting more experience with the various broken direct-to-ioctl > | termios2 hacks using Fedora 43 beta, I have found a fair number of > | cases where the software would fail to set, or clear CIBAUD for > | ... 29 lines of the commit log omitted. > > Produces 2 regressions: > | > | regressions.sum: > | Running gdb:gdb.base/term.exp ... > | FAIL: gdb.base/term.exp: after last resume: info terminal > | FAIL: gdb.base/term.exp: post tcsetattr: info terminal > > Used configuration : > *CI config* tcwg_gnu_native_check_gdb 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-1753. 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-arm-build/2297/… > 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-arm-build/2297/… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/2297/… > > Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/2297/… > Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/2296/… > > 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=8d999a6993611d375adc…

1 day, 19 hours

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!

2 days, 20 hours

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

3 days, 18 hours

Re: [Linaro-TCWG-CI] llvmorg-22-init-14324-g02c68b3ef754: 1 regression 3 fixes on aarch64

by Luke Lau

Hi there, thanks for picking up on this change. I see there’s 1 regression and 3 fixes, I just want to check are the fixes previous miscompiles? Thanks, Luke > On 17 Nov 2025, at 09: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 tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld, after: > | commit llvmorg-22-init-14324-g02c68b3ef754 > | Author: Luke Lau <luke(a)igalia.com> > | Date: Wed Nov 12 19:14:53 2025 +0800 > | > | [VPlan] Plumb scalable register size through narrowInterleaveGroups (#167505) > | > | On RISC-V narrowInterleaveGroups doesn't kick in because the wrong > | VectorRegWidth is passed to isConsecutiveInterleaveGroup. > | > | ... 10 lines of the commit log omitted. > > Produces 1 regression 3 fixes: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0363 ... > | FAIL: test-suite :: Fujitsu/Fortran/0363/Fujitsu-Fortran-0363_0283.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/0105 ... > | FAIL: test-suite :: Fujitsu/Fortran/0105/Fujitsu-Fortran-0105_0091.test > | ... and 2 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-2121. 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/02c68b3ef7544b875da4052dfb58205…

4 days, 6 hours

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

1 week, 2 days

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

1 week, 3 days

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

by Sam James

-> PR122575.

2 weeks, 1 day

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

2 weeks, 1 day

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain November 2025