- linaro-toolchain - lists.linaro.org

by Peter Maydell

Progress (short week, 3 days): * UM-2 [QEMU upstream maintainership] - more softfreeze related work: tagged rc0 this week - spent some time looking through Huawei's FEAT_NMI patchset; this is in basically good shape but there are a number of minor bugs/missing bits of the feature for them to work through still - reviewed a patchset adding nucleo-g071rb (an STM32G0 based board) -- PMM

1 year, 1 month

1
0
0 0

LLVM buildbot clang-aarch64-full-2stage

by orlando.hyams＠sony.com

Hi, I noticed this address registered as the admin for this LLVM buildbot - https://lab.llvm.org/buildbot/#/workers/134). I caused a failure at the start of the week (https://lab.llvm.org/buildbot/#/builders/179/builds/9629). I think it's a build (or test) configuration problem as outlined in this small PR https://github.com/llvm/llvm-zorg/pull/139. I can see the bot is currently failing now too (https://lab.llvm.org/buildbot/#/builders/179/builds/9681). I haven't looked at it closely but given the same tests are failing in a similar way (a different bitcode error from LLD), I imagine that might also be fixed by my llvm-zorg pull request above? Please can someone look at the llvm-zorg pull request when you have a spare moment? I have my LLVM change that caused the initial failure reverted in the meantime. Thanks, Orlando

1 year, 1 month

2
2
0 0

Re: [Linaro-TCWG-CI] gcc-14-9478-gdf483ebd246: FAIL: 7 regressions on aarch64

by Jonathan Wakely

Oops. Jakub has fixed this now. On Thu, 14 Mar 2024 at 23:45, <ci_notify(a)linaro.org> wrote: > > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1177 , please let us know if you are looking at the problem and/or when you have a fix. > > In gcc_check master-aarch64 after: > > | commit gcc-14-9478-gdf483ebd246 > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Mon Feb 26 13:17:13 2024 +0000 > | > | libstdc++: Add nodiscard in <algorithm> > | > | Add the [[nodiscard]] attribute to several functions in <algorithm>. > | These all have no side effects and are only called for their return > | value (e.g. std::count) or produce a result that must not be discarded > | for correctness (e.g. std::remove). > | > | ... 49 lines of the commit log omitted. > > FAIL: 7 regressions > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/torture/dg-torture.exp ... > FAIL: g++.dg/torture/pr104601.C -O0 (test for excess errors) > FAIL: g++.dg/torture/pr104601.C -O1 (test for excess errors) > FAIL: g++.dg/torture/pr104601.C -O2 (test for excess errors) > FAIL: g++.dg/torture/pr104601.C -O2 -flto -fno-use-linker-plugin -flto-partition=none (test for excess errors) > FAIL: g++.dg/torture/pr104601.C -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects (test for excess errors) > FAIL: g++.dg/torture/pr104601.C -O3 -g (test for excess errors) > FAIL: g++.dg/torture/pr104601.C -Os (test for excess errors) > ... and 1 more entries > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1715/artifac… > The full lists of regressions and progressions as well as configure and make commands are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1715/artifac… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1715/artifac… > > The configuration of this build is: > CI config tcwg_gcc_check master-aarch64 > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1715/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1714/artifac… > > Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://github.com/gcc-mirror/gcc/commit/df483ebd24689a3bebfae2089637a00eca… > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-aarch64 > *** FAIL: 7 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1715/artifac…

1 year, 2 months

1
0
0 0

[ACTIVITY] report week ending 14 Mar

by Peter Maydell

Progress (short week, 3 days): * UM-2 [QEMU upstream maintainership] - softfreeze week this week, so a lot of time shepherding patches and pullrequests upstream, looking to see if we have any bugs that we ought to fix for 9.0, etc - looked at our Coverity results and submitted patches for seven random easy-to-fix issues -- PMM

1 year, 2 months

1
0
0 0

[Linaro-TCWG-CI] glibc-2.39.9000-100-g2367bf468c: FAIL: 1 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. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. We track this report status in https://linaro.atlassian.net/browse/GNU-1176 , please let us know if you are looking at the problem and/or when you have a fix. In master-arm after: | commit glibc-2.39.9000-100-g2367bf468c | Author: Joseph Myers <josmyers(a)redhat.com> | Date: Wed Mar 13 19:46:21 2024 +0000 | | Update kernel version to 6.8 in header constant tests | | This patch updates the kernel version in the tests tst-mman-consts.py, | tst-mount-consts.py and tst-pidfd-consts.py to 6.8. (There are no new | constants covered by these tests in 6.8 that need any other header | changes.) | | ... 1 lines of the commit log omitted. FAIL: 1 regressions regressions.sum: === glibc tests === Running glibc:misc ... FAIL: misc/tst-pidfd-consts You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/623… The full lists of regressions and progressions as well as configure and make commands are in - https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/623… The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/623… The configuration of this build is: CI config tcwg_gnu_native_check_glibc master-arm -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/623… Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/622… Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=2367bf468ce43801de98… List of configurations that regressed due to this commit : * tcwg_gnu_native_check_glibc ** master-arm *** FAIL: 1 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… *** https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/623…

1 year, 2 months

1
0
0 0

Re: [Linaro-TCWG-CI] gdb-14-branchpoint-1411-g033bc67bdb0: FAIL: 2 regressions on arm

by Maxim Kuvyrkov

> On Jan 30, 2024, at 23: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. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1136 , please let us know if you are looking at the problem and/or when you have a fix. > > In master-arm after: > > | commit gdb-14-branchpoint-1411-g033bc67bdb0 > | Author: Tom Tromey <tom(a)tromey.com> > | Date: Tue Sep 19 17:39:31 2023 -0600 > | > | Only search types in cp_lookup_rtti_type > | > | This changes cp_lookup_rtti_type to only search for types -- not > | functions or variables. Due to the symbol-matching hack, this could > | just use SEARCH_TYPE_DOMAIN, but I think it's better to be clear; also > | I hold on to some hope that perhaps the hack can someday be removed. > > FAIL: 2 regressions > > regressions.sum: > === libstdc++ tests === > > Running libstdc++:libstdc++-prettyprinters/prettyprinters.exp ... > FAIL: libstdc++-prettyprinters/cxx11.cc print ecmiaow > FAIL: libstdc++-prettyprinters/cxx11.cc print emiaow Hi Tom, Hi Jonathan, After the above GDB patch I see 2 new failures both for aarch64-linux-gnu and arm-linux-gnueabihf in GCC's libstdc++ testsuite. The log [1] says: === $35 = warning: RTTI symbol not found for class 'main::custom_cat' warning: RTTI symbol not found for class 'main::custom_cat' got: $35 = warning: RTTI symbol not found for class 'main::custom_cat' FAIL: libstdc++-prettyprinters/cxx11.cc print emiaow skipping: warning: RTTI symbol not found for class 'main::custom_cat' std::error_code = {std::_V2::error_category: 42} skipping: std::error_code = {std::_V2::error_category: 42} $36 = warning: RTTI symbol not found for class 'main::custom_cat' warning: RTTI symbol not found for class 'main::custom_cat' got: $36 = warning: RTTI symbol not found for class 'main::custom_cat' FAIL: libstdc++-prettyprinters/cxx11.cc print ecmiaow === Which way should I dig -- GDB or libstdc++? Does this look like libstdc++ testcase needs an update? [1] https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/l… Thanks! -- Maxim Kuvyrkov https://www.linaro.org > > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/987/a… > The full lists of regressions and progressions as well as configure and make commands are in > - https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/987/a… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/987/a… > > The configuration of this build is: > CI config tcwg_gnu_native_check_gcc master-arm > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/987/a… > Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/986/a… > > Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sh… > > Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=033bc67bdb0c7… > > List of configurations that regressed due to this commit : > * tcwg_gnu_native_check_gcc > ** master-arm > *** FAIL: 2 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sh… > *** https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/987/a…

1 year, 2 months

3
4
0 0

Re: [Linaro-TCWG-CI] gdb-14-branchpoint-1356-g7737b133640: FAIL: 1 regressions on arm

by Maxim Kuvyrkov

> On Jan 27, 2024, at 17:25, ci_notify(a)linaro.org wrote: > > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1121 , please let us know if you are looking at the problem and/or when you have a fix. > > In master-arm after: > > | commit gdb-14-branchpoint-1356-g7737b133640 > | Author: Tom Tromey <tromey(a)adacore.com> > | Date: Tue Jan 9 11:47:17 2024 -0700 > | > | Handle DW_AT_endianity on enumeration types > | > | A user found that gdb would not correctly print a field from an Ada > | record using the scalar storage order feature. We tracked this down > | to a combination of problems. > | > | First, GCC did not emit DW_AT_endianity on the enumeration type. > | ... 14 lines of the commit log omitted. > > FAIL: 1 regressions > > regressions.sum: > === gdb tests === > > Running gdb:gdb.ada/scalar_storage.exp ... > FAIL: gdb.ada/scalar_storage.exp: print V_BE Hi Tom, I see the above failure for both aarch64-linux-gnu and arm-linux-gnueabihf in our testing. The log shows ([1]): === Breakpoint 1, storage () at /home/tcwg-buildslave/workspace/tcwg_gnu_2/gdb/gdb/testsuite/gdb.ada/scalar_storage/storage.adb:53 53 Do_Nothing (V_LE'Address); -- START (gdb) print V_LE $1 = (value => 126, another_value => 12, color => green) (gdb) PASS: gdb.ada/scalar_storage.exp: print V_LE get_compiler_info: gcc-14-0-1 print V_BE $2 = (value => 126, another_value => 12, color => red) (gdb) FAIL: gdb.ada/scalar_storage.exp: print V_BE === Any idea what can be causing this? This failure happens in CI configurations where we track tip-of-trunk GCC. [1] https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/l… Thanks, -- Maxim Kuvyrkov https://www.linaro.org > > === Results Summary === > > 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/1076/… . > The full lists of regressions and progressions are in > - https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1076/… . > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1076/… . > > The configuration of this build is: > CI config tcwg_gnu_native_check_gdb master-arm > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1076/… > Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1075/… > > Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sh… > > Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=7737b1336402c… > > List of configurations that regressed due to this commit : > * tcwg_gnu_native_check_gdb > ** master-arm > *** FAIL: 1 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sh… > *** https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1076/…

1 year, 2 months

2
2
0 0

Re: [Linaro-TCWG-CI] gcc-14-8680-g2f14c0dbb78: FAIL: 3 regressions on arm

by Maxim Kuvyrkov

> On Feb 1, 2024, at 16:07, ci_notify--- via Gcc-regression <gcc-regression(a)gcc.gnu.org> wrote: > > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1140 , please let us know if you are looking at the problem and/or when you have a fix. > > In gcc_check master-arm after: > > | commit gcc-14-8680-g2f14c0dbb78 > | Author: Roger Sayle <roger(a)nextmovesoftware.com> > | Date: Thu Feb 1 06:10:42 2024 +0000 > | > | PR target/113560: Enhance is_widening_mult_rhs_p. > | > | This patch resolves PR113560, a code quality regression from GCC12 > | affecting x86_64, by enhancing the middle-end's tree-ssa-math-opts.cc > | to recognize more instances of widening multiplications. > | > | The widening multiplication perception code identifies cases like: > | ... 116 lines of the commit log omitted. > > FAIL: 3 regressions > > regressions.sum: > === gcc tests === > > Running gcc:gcc.target/arm/arm.exp ... > FAIL: gcc.target/arm/wmul-5.c scan-assembler umlal > FAIL: gcc.target/arm/wmul-6.c scan-assembler smlalbb > FAIL: gcc.target/arm/wmul-7.c scan-assembler umlal Hi Roger, Your patch seems to regress the above 3 tests for all 32-bit ARM targets (see [1]). Would you please check if the regressions can be avoided? For reference, here are configure options we use for arm-linux-gnueabihf cross-toolchain: [2]. [1] https://linaro.atlassian.net/browse/GNU-1140 [2] https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/1303/a… Thanks! -- Maxim Kuvyrkov https://www.linaro.org > > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1650/artifact/ar… > The full lists of regressions and progressions as well as configure and make commands are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1650/artifact/ar… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1650/artifact/ar… > > The configuration of this build is: > CI config tcwg_gcc_check master-arm > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1650/artifact/ar… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1649/artifact/ar… > > Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://github.com/gcc-mirror/gcc/commit/2f14c0dbb789852947cb58fdf7d3162413… > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-arm > *** FAIL: 3 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1650/artifact/ar…

1 year, 2 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-14-8492-g1a8261e047f: FAIL: 3 regressions on arm

by Maxim Kuvyrkov

> On Jan 30, 2024, at 00:35, ci_notify--- via Gcc-regression <gcc-regression(a)gcc.gnu.org> wrote: > > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1132 , please let us know if you are looking at the problem and/or when you have a fix. > > In gcc_check master-arm after: > > | commit gcc-14-8492-g1a8261e047f > | Author: Richard Sandiford <richard.sandiford(a)arm.com> > | Date: Mon Jan 29 12:33:08 2024 +0000 > | > | vect: Tighten vect_determine_precisions_from_range [PR113281] > | > | This was another PR caused by the way that > | vect_determine_precisions_from_range handles shifts. We tried to > | narrow 32768 >> x to a 16-bit shift based on range information for > | the inputs and outputs, with vect_recog_over_widening_pattern > | (after PR110828) adjusting the shift amount. But this doesn't > | ... 36 lines of the commit log omitted. > > FAIL: 3 regressions > > regressions.sum: > === gcc tests === > > Running gcc:gcc.target/arm/simd/simd.exp ... > FAIL: gcc.target/arm/simd/mve-vshr.c scan-assembler-times vneg.s[0-9]+\\tq[0-9]+, q[0-9]+ 6 > FAIL: gcc.target/arm/simd/mve-vshr.c scan-assembler-times vshl.s[0-9]+\\tq[0-9]+, q[0-9]+ 3 > FAIL: gcc.target/arm/simd/mve-vshr.c scan-assembler-times vshl.u[0-9]+\\tq[0-9]+, q[0-9]+ 3 Hi Richard, Could you please check whether the above tests need an update after your patch? We see these tests now consistently failing across all 32-bit ARM configurations that we track (see [1]). As an example, our configure options for arm-linux-gnueabihf that show the failure are at [2]. [1] https://linaro.atlassian.net/browse/GNU-1132 [2] https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/lastSuccessfulBu… Thanks! -- Maxim Kuvyrkov https://www.linaro.org > > === Results Summary === > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1636/artifact/ar… . > The full lists of regressions and progressions are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1636/artifact/ar… . > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1636/artifact/ar… . > > The configuration of this build is: > CI config tcwg_gcc_check master-arm > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1636/artifact/ar… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1635/artifact/ar… > > Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://github.com/gcc-mirror/gcc/commit/1a8261e047f7a2c2b0afb95716f7615cba… > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-arm > *** FAIL: 3 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1636/artifact/ar…

1 year, 2 months

1
0
0 0

[ACTIVITY] report week ending 8 Mar

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] - code review (softfreeze is next week!): + Add device STM32L4x5 RCC + Add support for I2C in BCM2835 boards + hw/scsi/lsi53c895a: add timer to scripts processing + target/arm: Do memory alignment check for device memory + linux-user: Implement some prctls + some minor patches fixing CI job breakage (FreeBSD 13.2 -> 13.3 change, Python has dropped 'distutils') + a patchset improving the robustness of the elf2dmp utility when fed a corrupt crashfile + get our Coverity Scan submission under gitlab CI control rather than a developer's work machine - summarised discussion about deprecating older Arm board models; sent out patch to mark deprecated all PXA2xx and OMAP2 boards, plus one OMAP1 board that we have no test images for - triaged some new Coverity issues * QEMU-530 [QEMU ARMv9.5 Baseline CPU for TCG] - Sent FEAT_ECV patchset out for code review, addressed minor review comments -- PMM

1 year, 2 months

1
0
0 0

Re: [Linaro-TCWG-CI] 2 patches in binutils: FAIL: 694 regressions on aarch64

by Christophe Lyon

On Tue, 5 Mar 2024 at 21:24, <ci_notify(a)linaro.org> wrote: > > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > In binutils_check master-aarch64 after: > > | 2 patches in binutils > | Patchwork URL: https://patchwork.sourceware.org/patch/86798 > | 0fe0a00e217 aarch64: Add support for SVE ADDPT, SUBPT, MADPT, MLAPT instructions > | b9319f64d9a aarch64: Add support for (M)ADDPT and (M)SUBPT instructions > | ... applied on top of baseline commit: > | f08311ceb1b gdb/testsuite: fix duplicate test names in gdb.trace/circ.exp > > FAIL: 694 regressions > Hi Yury, Please consider this notification as a false alarm: our precommit CI does not regenerate files such as aarch64-*-2.c, as required by your patches, thus leading to the tests failures reported here. You may have seen the discussion I started a few days ago about --enable-maintainer-mode being broken. Thanks, Christophe > regressions.sum: > === binutils tests === > > Running binutils:binutils-all/aarch64/aarch64.exp ... > FAIL: Check if efi app format is recognized > FAIL: Disassembler detects unallocated instruction encodings. > === gas tests === > > Running gas:gas/aarch64/aarch64.exp ... > FAIL: AArch64 Bignums in Literal Pool (PR 16688) > FAIL: AArch64 Mapping Symbols > ... and 718 more entries > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/116… > The full lists of regressions and progressions as well as configure and make commands are in > - https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/116… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/116… > > The configuration of this build is: > CI config tcwg_binutils_check master-aarch64 > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/116… > Reference build : https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-build/838/art… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files.

1 year, 2 months

2
1
0 0

Re: [Linaro-TCWG-CI] gcc-14-9268-g574fd1f17f1: FAIL: 15 regressions: 15 progressions on aarch64

by Christophe Lyon

Hi Patrick, This report can be considered as a false alarm: the errors were already present in the baseline, but the ICE line number changed since your patch modified the code in the file where the ICE occurs. That being said, I've noticed another report saying that your patch broke bootstrap on i686. Thanks, Christophe On Sat, 2 Mar 2024 at 20:38, <ci_notify(a)linaro.org> wrote: > > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1168 , please let us know if you are looking at the problem and/or when you have a fix. > > In master-aarch64 after: > > | commit gcc-14-9268-g574fd1f17f1 > | Author: Patrick Palka <ppalka(a)redhat.com> > | Date: Fri Mar 1 17:24:15 2024 -0500 > | > | c++/modules: depending local enums [PR104919, PR106009] > | > | For local enums defined in a non-template function or a function template > | instantiation it seems we neglect to make the function depend on the enum > | definition (which modules considers logically separate), which ultimately > | causes the enum definition to not be properly streamed before uses > | within the function definition are streamed. > | ... 75 lines of the commit log omitted. > > FAIL: 15 regressions: 15 progressions > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/modules/modules.exp ... > FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6113) > FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2a (internal compiler error: in core_vals, at cp/module.cc:6113) > FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6113) > FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6113) > FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2a (internal compiler error: in core_vals, at cp/module.cc:6113) > FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6113) > FAIL: g++.dg/modules/xtreme-header-5_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6113) > ... and 9 more entries > > progressions.sum: > === g++ tests === > > Running g++:g++.dg/modules/modules.exp ... > FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2a (internal compiler error: in core_vals, at cp/module.cc:6114) > FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6114) > FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6114) > FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6114) > FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2a (internal compiler error: in core_vals, at cp/module.cc:6114) > FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6114) > FAIL: g++.dg/modules/xtreme-header-5_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6114) > ... and 9 more entries > > 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/9… > The full lists of regressions and progressions as well as configure and make commands are in > - https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/9… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/9… > > The configuration of this build is: > CI config tcwg_gnu_native_check_gcc master-aarch64 > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/9… > Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/9… > > Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://github.com/gcc-mirror/gcc/commit/574fd1f17f100c7c355ad26bc525ab5a33… > > List of configurations that regressed due to this commit : > * tcwg_gnu_native_check_gcc > ** master-aarch64 > *** FAIL: 15 regressions: 15 progressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/9…

1 year, 2 months

1
0
0 0

[ACTIVITY] report week ending 1 Mar

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] - code review, notably another round of the raspberry pi 4b emulation series. Reviewed and took a subset of the patches, which is enough to get a working model without PCI or ethernet. We'll work on the landing other parts, but no need to block the initial model on them. * QEMU-530 [QEMU ARMv9.5 Baseline CPU for TCG] - Started implementation of FEAT_ECV (enhanced counter virtualization); I have a preliminary set of patches which I am currently testing and hope to be able to send out early next week -- PMM

1 year, 2 months

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-19-init-3481-g8c2ae42b3e1c: Failure on aarch64

by Nathan Chancellor

On Wed, Feb 28, 2024 at 02:47:11PM +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. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/LLVM-1153 , please let us know if you are looking at the problem and/or when you have a fix. > > In CI config tcwg_kernel/llvm-master-aarch64-lts-allyesconfig after: > > | commit llvmorg-19-init-3481-g8c2ae42b3e1c > | Author: Kupa-Martin <84517188+Kupa-Martin(a)users.noreply.github.com> > | Date: Tue Feb 27 11:58:59 2024 -0300 > | > | [Clang][Sema] Fix missing warning when comparing mismatched enums in … (#81418) > | > | …C mode > | > | Factored logic from `CheckImplicitConversion` into new methods > | `Expr::getEnumConstantDecl` and `Expr::getEnumCoercedType` for use in > | `checkEnumArithmeticConversions`. > | ... 2 lines of the commit log omitted. > > Results changed to > # reset_artifacts: > -10 > # build_abe binutils: > -9 > # build_kernel_llvm: > -5 > # build_abe qemu: > -2 > # linux_n_obj: > 37 > > From > # reset_artifacts: > -10 > # build_abe binutils: > -9 > # build_kernel_llvm: > -5 > # build_abe qemu: > -2 > # linux_n_obj: > 22291 > > The configuration of this build is: > CI config tcwg_kernel/llvm-master-aarch64-lts-allyesconfig > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-lts-allyesconfig… > Reference build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-lts-allyesconfig… > > Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > > Full commit : https://github.com/llvm/llvm-project/commit/8c2ae42b3e1c6aa7c18f873edcebff7… > > List of configurations that regressed due to this commit : > * tcwg_kernel > ** llvm-master-aarch64-lts-allyesconfig > *** Failure > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > *** https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-lts-allyesconfig… Thanks a lot for the report, this is expected with that change. How we want to handle this in the kernel is currently under discussion at https://github.com/ClangBuiltLinux/linux/issues/2002. Cheers, Nathan

1 year, 2 months

1
0
0 0

Re: [Linaro-TCWG-CI] 6 patches in binutils: FAIL: 1 regressions on aarch64

by Jan Beulich

On 23.02.2024 15:24, ci_notify(a)linaro.org wrote: > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. So: The specific failure observed makes me guess that in the course of building generated files (opcodes/aarch64-*-2.c) aren't re-generated. If this is indeed the case, sending out such unsolicited emails (I've had a 2nd one in the meantime, for whatever reason) is a waste of everybody's time, even more so when not clearly indicating that fact, such that - quoting above - it is possible "within minutes" to understand what's going on / wrong. IOW - unless clarified I'm going to assume that the report here is a false negative. Jan > In binutils_check master-aarch64 after: > > | 6 patches in binutils > | Patchwork URL: https://patchwork.sourceware.org/patch/86276 > | 2d039d3b147 gas/NEWS: drop mention of Arm64's SVE2.1 and SME2.1 > | 38eca7294bd Arm64: correct SVE2.1 ld2q (scalar plus scalar) > | cb804986590 Arm64: correct SVE2.1 ld{3,4}q / st{3,4}q (scalar plus immediate) > | edaf01ca3b4 Arm64: check tied operand specifier in aarch64-gen > | 006ce007bc8 Arm64: check matching operands for predicated B16B16 insns > | ... and 1 more patches in binutils > | ... applied on top of baseline commit: > | e346d50a891 x86: rename vec_encoding and vex_encoding_* > > FAIL: 1 regressions > > regressions.sum: > === gas tests === > > Running gas:gas/aarch64/aarch64.exp ... > FAIL: Test of SVE2.1 instructions > > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/109… > The full lists of regressions and progressions as well as configure and make commands are in > - https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/109… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/109… > > The configuration of this build is: > CI config tcwg_binutils_check master-aarch64 > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/109… > Reference build : https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-build/797/art…

1 year, 2 months

2
3
0 0

[ACTIVITY] report week ending 23 Feb

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] - code review - finished and sent out for review the patchset that provides a 3-phase-reset version of qemu_register_reset() - The MSYS2 project are dropping their support for 32-bit Windows, which affects QEMU because we use them for our "test build on Windows" CI jobs. This prompted us to drop our 32-bit Windows host support (which conveniently we'd already deprecated last year). Sent out patches to drop the CI jobs, document that it's not a supported platform, etc. thanks -- PMM

1 year, 2 months

1
0
0 0

llvm lldb-aarch64-windows builder failing

by Ted Woodward

I apologize if this is the wrong email for this report. I got it from the "Worker" tab on a build on https://lab.llvm.org/buildbot/#/builders/219 . The build is failing at the build step. It's trying to run: ninja ^"^" ^"^" which is erroring out with ninja: error: empty path https://lab.llvm.org/buildbot/#/builders/219/builds/9644/steps/4/logs/stdio Ted

1 year, 2 months

2
1
0 0

Re: [Linaro-TCWG-CI] gdb patch #85948: FAIL: 7 regressions: 1 progressions on arm

by Tiezhu Yang

On 02/21/2024 03:52 AM, ci_notify(a)linaro.org wrote: > If you can't get what you need from our CI within minutes, let us know and we will be happy to help. We can see "Operation not permitted" in the log info, please try one of the following processes to test: (1) set ptrace_scope as 0 $ echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope $ make check-gdb TESTS="gdb.threads/attach-many-short-lived-threads.exp" (2) use sudo $ sudo make check-gdb TESTS="gdb.threads/attach-many-short-lived-threads.exp" Thanks, Tiezhu

1 year, 2 months

2
3
0 0

Re: [Linaro-TCWG-CI] gcc-14-9028-g7f3d900684a: FAIL: 1 regressions: 1 progressions on aarch64

by Jonathan Wakely

On Fri, 16 Feb 2024 at 19: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. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1155 , please let us know if you are looking at the problem and/or when you have a fix. Reported as https://gcc.gnu.org/PR113961 and fixed. > In gcc_check master-aarch64 after: > > | commit gcc-14-9028-g7f3d900684a > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Wed Feb 7 11:31:10 2024 +0000 > | > | libstdc++: Fix FAIL: 26_numerics/random/pr60037-neg.cc [PR113931] > | > | PR libstdc++/87744 > | PR libstdc++/113931 > | > | libstdc++-v3/ChangeLog: > | > | ... 2 lines of the commit log omitted. > > FAIL: 1 regressions: 1 progressions > > regressions.sum: > === libstdc++ tests === > > Running libstdc++:libstdc++-dg/conformance.exp ... > FAIL: 26_numerics/random/pr60037-neg.cc -std=gnu++17 (test for errors, line 3350) > > > progressions.sum: > === libstdc++ tests === > > Running libstdc++:libstdc++-dg/conformance.exp ... > FAIL: 26_numerics/random/pr60037-neg.cc -std=gnu++17 (test for errors, line 271) > > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1615/artifac… > The full lists of regressions and progressions as well as configure and make commands are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1615/artifac… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1615/artifac… > > The configuration of this build is: > CI config tcwg_gcc_check master-aarch64 > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1615/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1614/artifac… > > Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://github.com/gcc-mirror/gcc/commit/7f3d900684ad989164114f25eb46a33871… > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-aarch64 > *** FAIL: 1 regressions: 1 progressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1615/artifac…

1 year, 2 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-14-8998-gc9ce332b557: FAIL: 2 regressions on aarch64

by Jonathan Wakely

On Thu, 15 Feb 2024 at 21: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. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1154 , please let us know if you are looking at the problem and/or when you have a fix. Also reported as https://gcc.gnu.org/PR113931 and now fixed. > > In gcc_check master-aarch64 after: > > | commit gcc-14-8998-gc9ce332b557 > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Wed Feb 7 11:31:10 2024 +0000 > | > | libstdc++: Use 128-bit arithmetic for std::linear_congruential_engine [PR87744] > | > | For 32-bit targets without __int128 we need to implement the LCG > | transition function by hand using 64-bit types. > | > | We can also slightly simplify the __mod function by using if-constexpr > | unconditionally, disabling -Wc++17-extensions warnings with diagnostic > | ... 13 lines of the commit log omitted. > > FAIL: 2 regressions > > regressions.sum: > === libstdc++ tests === > > Running libstdc++:libstdc++-dg/conformance.exp ... > FAIL: 26_numerics/random/pr60037-neg.cc -std=gnu++17 (test for errors, line 271) > FAIL: 26_numerics/random/pr60037-neg.cc -std=gnu++17 (test for excess errors) > > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1609/artifac… > The full lists of regressions and progressions as well as configure and make commands are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1609/artifac… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1609/artifac… > > The configuration of this build is: > CI config tcwg_gcc_check master-aarch64 > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1609/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1608/artifac… > > Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://github.com/gcc-mirror/gcc/commit/c9ce332b557bb95987d038d98ea929cdfd… > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-aarch64 > *** FAIL: 2 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1609/artifac…

1 year, 2 months

1
0
0 0

Fwd: [Linaro-TCWG-CI] glibc patch #85585: FAIL: 1 regressions on arm

by H.J. Lu

FAIL: elf/tst-gnu2-tls2 indicates that your _dl_tlsdesc_dynamic may not preserve all caller-saved registers. Please find out how the test fails. H.J. ---------- Forwarded message --------- From: <ci_notify(a)linaro.org> Date: Wed, Feb 14, 2024 at 3:50 PM Subject: [Linaro-TCWG-CI] glibc patch #85585: FAIL: 1 regressions on arm To: <hjl.tools(a)gmail.com> Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. In glibc_check master-arm after: | glibc patch https://patchwork.sourceware.org/patch/85585 | Author: H.J. Lu <hjl.tools(a)gmail.com> | Date: Sun Feb 11 19:19:49 2024 -0800 | | x86-64: Update _dl_tlsdesc_dynamic to preserve vector registers | | Compiler generates the following instruction sequence for GNU2 dynamic | TLS access: | | leaq tls_var@TLSDESC(%rip), %rax | call *tls_var@TLSCALL(%rax) | ... 13 lines of the commit log omitted. | ... applied on top of baseline commit: | dbae3a3940 trivial doc fix: remove weird phrase "syscall takes zero to five arguments" FAIL: 1 regressions regressions.sum: === glibc tests === Running glibc:elf ... FAIL: elf/tst-gnu2-tls2 You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/1460/artif… The full lists of regressions and progressions as well as configure and make commands are in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/1460/artif… The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/1460/artif… The configuration of this build is: CI config tcwg_glibc_check master-arm -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/1460/artif… Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/953/artifact/a… -- H.J.

1 year, 2 months

3
7
0 0

Re: [Linaro-TCWG-CI] glibc patch #85772: FAIL: 1 regressions on aarch64

by H.J. Lu

On Thu, Feb 15, 2024 at 11:36 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. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > In glibc_check master-aarch64 after: > > | glibc patch https://patchwork.sourceware.org/patch/85772 > | Author: H.J. Lu <hjl.tools(a)gmail.com> > | Date: Thu Feb 15 03:27:19 2024 -0800 > | > | sort-makefile-lines.py: Allow '_' in name and "^# name" > | > | '_' is used in Makefile variable names and many variables end with > | "^# name". Relax sort-makefile-lines.py to allow '_' in name and > | "^# name" as variable end. This fixes BZ #31385. > | ... applied on top of baseline commit: > | dbae3a3940 trivial doc fix: remove weird phrase "syscall takes zero to five arguments" > > FAIL: 1 regressions > > regressions.sum: > === glibc tests === > > Running glibc:. ... > FAIL: lint-makefiles > > > Should be fixed now. -- H.J.

1 year, 2 months

1
0
0 0

[ACTIVITY] report week ending 15 Feb

by Peter Maydell

Progress (short week, 3 days): * UM-2 [QEMU upstream maintainership] - various bits of cleanup and maintainer stuff - working on a 3-phase-reset-aware equivalent to qemu_register_reset(): have some basically working code, need to tidy it up and look for where the changes it makes to reset ordering might break things - sent out an email proposing that we deprecate-and-drop the pxa2xx, omap and strongarm boards. This has at least produced a useful conversation that's clarified which of these models people are using as part of their Linux kernel testing or development process. I'd still like to drop some of them if we can, though... -- PMM

1 year, 2 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc patch #85713: FAIL: 19 regressions on arm

by Maxim Kuvyrkov

Hi Richard, This is a false positive. We had a bit of instability in our CI yesterday, and it should be all fixed now. Thanks, -- Maxim Kuvyrkov https://www.linaro.org > On Feb 14, 2024, at 23:00, ci_notify(a)linaro.org wrote: > > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > In gcc_check master-arm after: > > | gcc patch https://patchwork.sourceware.org/patch/85713 > | Author: Richard Biener <rguenther(a)suse.de> > | Date: Wed Feb 14 13:02:56 2024 +0100 > | > | tree-optimization/113910 - huge compile time during PTA > | > | For the testcase in PR113910 we spend a lot of time in PTA comparing > | bitmaps for looking up equivalence class members. This points to > | the very weak bitmap_hash function which effectively hashes set > | and a subset of not set bits. The following improves it by mixing > | that weak result with the population count of the bitmap, reducing > | ... 19 lines of the commit log omitted. > | ... applied on top of baseline commit: > | a032c319cb9 testsuite: gdc: Require ucn in gdc.test/runnable/mangle.d etc. [PR104739] > > FAIL: 19 regressions > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/dg.exp ... > FAIL: c-c++-common/pr44832.c -std=gnu++17 (test for excess errors) > FAIL: c-c++-common/pr44832.c -std=gnu++98 (test for excess errors) > FAIL: g++.dg/opt/pr100541-2.C -std=gnu++14 (test for excess errors) > FAIL: g++.dg/opt/pr100541-2.C -std=gnu++17 (test for excess errors) > FAIL: g++.dg/opt/pr100541-2.C -std=gnu++20 (test for excess errors) > > Running g++:g++.dg/pch/pch.exp ... > ... and 29 more entries > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/6118/artifac… > The full lists of regressions and progressions as well as configure and make commands are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/6118/artifac… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/6118/artifac… > > The configuration of this build is: > CI config tcwg_gcc_check master-arm > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/6118/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1717/artifact/ar…

1 year, 2 months

1
0
0 0

[Linaro-TCWG-CI] binutils-2_41-release-2297-g313f04b6edc: FAIL: 1 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. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. We track this report status in https://linaro.atlassian.net/browse/GNU-1153 , please let us know if you are looking at the problem and/or when you have a fix. In binutils_check master-arm after: | commit binutils-2_41-release-2297-g313f04b6edc | Author: Alan Modra <amodra(a)gmail.com> | Date: Thu Feb 15 19:03:07 2024 +1030 | | Re: elf_backend_finish_dynamic_symbol returning false | | I didn't examine ld testsuite logs properly after cf95b909e2c2. | Replacing one of the "return false" with BFD_ASSERT in | finish_dynamic_symbol was wrong as it causes segmentation faults on | testcases expected to fail. Revert those changes and instead make | a bfd_final_link failure noisy. FAIL: 1 regressions regressions.sum: === ld tests === Running ld:ld-arm/arm-elf.exp ... FAIL: non-contiguous-arm7 You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_binutils_check--master-arm-build/776/artifac… The full lists of regressions and progressions as well as configure and make commands are in - https://ci.linaro.org/job/tcwg_binutils_check--master-arm-build/776/artifac… The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_binutils_check--master-arm-build/776/artifac… The configuration of this build is: CI config tcwg_binutils_check master-arm -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_binutils_check--master-arm-build/776/artifac… Reference build : https://ci.linaro.org/job/tcwg_binutils_check--master-arm-build/775/artifac… Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti… Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=313f04b6edcd0… List of configurations that regressed due to this commit : * tcwg_binutils_check ** master-arm *** FAIL: 1 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti… *** https://ci.linaro.org/job/tcwg_binutils_check--master-arm-build/776/artifac…

1 year, 2 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain