- linaro-toolchain - lists.linaro.org

Re: [Linaro-TCWG-CI] gcc-15-1500-g1340ddea015: FAIL: 2 regressions on arm

by Maxim Kuvyrkov

Hi Matthias, Looking at [1], we are seeing this error only for bare-metal 32-bit ARM target, which, I believe, is not a configuration that compiler explorer supports. The specific configurations are either soft-float, or target ARM cores without NEON (aka no SIMD FPU). Maybe the test should be guarded on the target supporting vectorization? I.e., maybe add // { dg-require-effective-target vect_int } ? [1] https://linaro.atlassian.net/browse/GNU-1265 -- Maxim Kuvyrkov https://www.linaro.org > On Jun 21, 2024, at 19:03, Matthias Kretz via Gcc-regression <gcc-regression(a)gcc.gnu.org> wrote: > > Hi, > > I looked into this and still don't understand how to reproduce it. > > The issue as logged in libstdc++.log is a call from > find_last_set(simd_mask<int, _VecBuiltin<16>>) to > _MaskImplNeonMixin::_S_to_bits, which calls vpadd_s32 with two > [[gnu::vector_size(8)]] int arguments. The CI compiler complains "error: > cannot convert '__vector(2) int' to 'int32x2_t'". > > Why is that an error on your side and not on any compiler I have at hand? > > https://compiler-explorer.com/z/88WhcM7Kb not an error here. > > In any case, the new test only exposes an existing issue in the <experimental/ > simd> implementation (or its interaction with some variants of GCC?). The > change did not introduce a new bug to libstdc++. > > Best, > Matthias > > > On Friday, 21 June 2024 17:00:23 GMT+2 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-1265 >> , please let us know if you are looking at the problem and/or when you have >> a fix. >> In arm-eabi v7-a softfp after: >> | commit gcc-15-1500-g1340ddea015 >> | Author: Matthias Kretz <m.kretz(a)gsi.de> >> | Date: Fri Jun 14 15:11:25 2024 +0200 >> | >> | libstdc++: Fix find_last_set(simd_mask) to ignore padding bits >> | >> | With the change to the AVX512 find_last_set implementation, the >> | change >> | to AVX512 operator!= is unnecessary. However, the latter was not >> | producing optimal code and unnecessarily set the padding bits. In >> | theory, the compiler could determine that with the new != >> | implementation, the bit operation for clearing the padding bits is a >> | >> | ... 13 lines of the commit log omitted. >> >> FAIL: 2 regressions >> >> regressions.sum: >> === libstdc++ tests === >> >> Running libstdc++:libstdc++-dg/conformance.exp ... >> FAIL: experimental/simd/pr115454_find_last_set.cc -mfpu=neon -ffast-math -O2 >> -Wno-psabi (test for excess errors) UNRESOLVED: >> experimental/simd/pr115454_find_last_set.cc -mfpu=neon -ffast-math -O2 >> -Wno-psabi compilation failed to produce executable >> >> >> You can find the failure logs in *.log.1.xz files in >> - >> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e >> abi-build/512/artifact/artifacts/00-sumfiles/ The full lists of regressions >> and progressions as well as configure and make commands are in - >> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e >> abi-build/512/artifact/artifacts/notify/ The list of [ignored] baseline and >> flaky failures are in >> - >> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e >> abi-build/512/artifact/artifacts/sumfiles/xfails.xfail >> >> The configuration of this build is: >> CI config tcwg_gnu_embed_check_gcc arm-eabi -marm -march=armv7-a >> -mfpu=vfpv3-d16 -mfloat-abi=softfp >> >> -----------------8<--------------------------8<--------------------------8<- >> ------------------------- The information below can be used to reproduce a >> debug environment: >> >> Current build : >> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e >> abi-build/512/artifact/artifacts Reference build : >> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e >> abi-build/511/artifact/artifacts >> >> Reproduce last good and first bad builds: >> https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh >> a1/1340ddea0158de3f49aeb75b4013e5fc313ff6f4/tcwg_gnu_embed_check_gcc/master- >> arm_v7a_softfp_eabi/reproduction_instructions.txt >> >> Full commit : >> https://github.com/gcc-mirror/gcc/commit/1340ddea0158de3f49aeb75b4013e5fc31 >> 3ff6f4 >> >> List of configurations that regressed due to this commit : >> * tcwg_gnu_embed_check_gcc >> ** master-arm_v7a_softfp_eabi >> *** FAIL: 2 regressions >> *** >> https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh >> a1/1340ddea0158de3f49aeb75b4013e5fc313ff6f4/tcwg_gnu_embed_check_gcc/master- >> arm_v7a_softfp_eabi/details.txt *** >> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e >> abi-build/512/artifact/artifacts > > > -- > ────────────────────────────────────────────────────────────────────────── > Dr. Matthias Kretz https://mattkretz.github.io > GSI Helmholtz Center for Heavy Ion Research https://gsi.de > std::simd > ──────────────────────────────────────────────────────────────────────────

1 year

1
0
0 0

[ACTIVITY] report week ending 21 Jun

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] + code review and target-arm pullreq + Coverity gardening: triage of new issues; update of component definitions + respin of "allow a second UART in virt machine" patchset from last year + KVM Forum programme committee work -- PMM

1 year

1
0
0 0

clang-arm64-windows-msvc cannot checkout LLVM

by Galina Kistanova

Hello Linaro Toolchain Working Group, clang-arm64-windows-msvc cannot checkout LLVM because of this error: fatal: Unable to create 'C:/Users/tcwg/llvm-worker/clang-arm64-windows-msvc/llvm/.git/index.lock': File exists. Looks like it needs some love and care. Could you look at this, please? Thanks Galina

1 year

2
2
0 0

[Linaro-TCWG-CI] glibc-2.39.9000-340-g176671f604: FAIL: 1 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. 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-1261 , please let us know if you are looking at the problem and/or when you have a fix. In glibc_check master-aarch64 after: | commit glibc-2.39.9000-340-g176671f604 | Author: Carlos Llamas <cmllamas(a)google.com> | Date: Tue Jun 18 10:56:34 2024 +0200 | | linux: add definitions for hugetlb page size encodings | | A desired hugetlb page size can be encoded in the flags parameter of | system calls such as mmap() and shmget(). The Linux UAPI headers have | included explicit definitions for these encodings since v4.14. | | This patch adds these definitions that are used along with MAP_HUGETLB | ... 14 lines of the commit log omitted. FAIL: 1 regressions regressions.sum: === glibc tests === Running glibc:misc ... FAIL: misc/tst-mman-consts You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/1479/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-aarch64-build/1479/artif… The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/1479/artif… The configuration of this build is: CI config tcwg_glibc_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_glibc_check--master-aarch64-build/1479/artif… Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/1478/artif… 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=176671f6042912200ea9… List of configurations that regressed due to this commit : * tcwg_glibc_check ** master-aarch64 *** FAIL: 1 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… *** https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/1479/artif…

1 year

4
4
0 0

[Linaro-TCWG-CI] glibc-2.39.9000-328-g7ec903e028: FAIL: 12 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-1260 , please let us know if you are looking at the problem and/or when you have a fix. In glibc_check master-arm after: | commit glibc-2.39.9000-328-g7ec903e028 | Author: Joseph Myers <josmyers(a)redhat.com> | Date: Mon Jun 17 16:31:49 2024 +0000 | | Implement C23 exp2m1, exp10m1 | | C23 adds various <math.h> function families originally defined in TS | 18661-4. Add the exp2m1 and exp10m1 functions (exp2(x)-1 and | exp10(x)-1, like expm1). | | As with other such functions, these use type-generic templates that | ... 33 lines of the commit log omitted. FAIL: 12 regressions regressions.sum: === glibc tests === Running glibc:math ... FAIL: math/test-double-exp10m1 FAIL: math/test-double-exp2m1 FAIL: math/test-float-exp10m1 FAIL: math/test-float-exp2m1 FAIL: math/test-float32-exp10m1 FAIL: math/test-float32-exp2m1 FAIL: math/test-float32x-exp10m1 ... and 6 more entries You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1444/artifact/… 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-build/1444/artifact/… The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1444/artifact/… 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-build/1444/artifact/… Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1442/artifact/… 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=7ec903e028271d029818… List of configurations that regressed due to this commit : * tcwg_glibc_check ** master-arm *** FAIL: 12 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… *** https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1444/artifact/…

1 year

1
0
0 0

[Linaro-TCWG-CI] glibc-2.39.9000-327-g55eb99e9a9: FAIL: 6 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-1259 , please let us know if you are looking at the problem and/or when you have a fix. In glibc_check master-arm after: | commit glibc-2.39.9000-327-g55eb99e9a9 | Author: Joseph Myers <josmyers(a)redhat.com> | Date: Mon Jun 17 13:48:13 2024 +0000 | | Implement C23 log10p1 | | C23 adds various <math.h> function families originally defined in TS | 18661-4. Add the log10p1 functions (log10(1+x): like log1p, but for | base-10 logarithms). | | This is directly analogous to the log2p1 implementation (except that | ... 6 lines of the commit log omitted. FAIL: 6 regressions regressions.sum: === glibc tests === Running glibc:math ... FAIL: math/test-double-log10p1 FAIL: math/test-float-log10p1 FAIL: math/test-float32-log10p1 FAIL: math/test-float32x-log10p1 FAIL: math/test-float64-log10p1 FAIL: math/test-ldouble-log10p1 You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1442/artifact/… 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-build/1442/artifact/… The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1442/artifact/… 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-build/1442/artifact/… Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1441/artifact/… 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=55eb99e9a9d840ba452b… List of configurations that regressed due to this commit : * tcwg_glibc_check ** master-arm *** FAIL: 6 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… *** https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1442/artifact/…

1 year

1
0
0 0

Multiple AArch64 stage2 buildbots failing due to: Unknown value for CMAKE_BUILD_TYPE: {stage2_config}

by Florian Hahn

Hi, it looks like there's an issue with some of the stage2 buildbot configurations. At least the following AArch64 stage-2 bots are failing during cmake for stage2: https://lab.llvm.org/buildbot/#/builders/41/builds/24 https://lab.llvm.org/buildbot/#/builders/84/builds/62 Both failing with CMake Error at CMakeLists.txt:425 (message): Unknown value for CMAKE_BUILD_TYPE: {stage2_config} Cheers, Florian

1 year

2
3
0 0

Re: [Linaro-TCWG-CI] gcc-15-1209-gc5e3be45688: Failure on aarch64

by David Malcolm

On Wed, 2024-06-12 at 20:25 +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/GNU-1254 , please let us know if > you are looking at the problem and/or when you have a fix. Sorry about the breakage. I had filed this as https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115465 and I believe I've fixed it with r15-1220- ge35f4eab68773b08324f9784ca69f8ace3c657cc. Dave > > In gcc_build master-aarch64 after: > > | commit gcc-15-1209-gc5e3be45688 > | Author: David Malcolm <dmalcolm(a)redhat.com> > | Date: Wed Jun 12 09:15:09 2024 -0400 > | > | pretty_printer: make all fields private > | > | No functional change intended. > | > | gcc/analyzer/ChangeLog: > | * access-diagram.cc (access_range::dump): Update for > fields of > | pretty_printer becoming private. > | ... 227 lines of the commit log omitted. > > Results changed to > # reset_artifacts: > -10 > # true: > 0 > # build_abe gcc: > # FAILED > # First few build errors in logs: > # 00:03:27 ../../../../../../gcc/gcc/config/aarch64/aarch64-early- > ra.cc:3449:23: error: ‘class pretty_printer’ has no member named > ‘buffer’; did you mean ‘output_buffer* pretty_printer::m_buffer’? > (not accessible from this context) > # 00:03:27 make[2]: *** [/home/tcwg- > buildslave/workspace/tcwg_gnu_3/abe/snapshots/gcc.git~master/gcc/conf > ig/aarch64/t-aarch64:200: aarch64-early-ra.o] Error 1 > # 00:03:27 make[1]: *** [Makefile:4704: all-gcc] Error 2 > # 00:03:27 make: *** [Makefile:1065: all] Error 2 > > From > # reset_artifacts: > -10 > # true: > 0 > # build_abe gcc: > 1 > > The configuration of this build is: > CI config tcwg_gcc_build 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_build--master-aarch64-build/2157/artifac… > Reference build : > https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/2156/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/c5e3be456888aa48f591512ec28183703e… > > List of configurations that regressed due to this commit : > * tcwg_gcc_build > ** master-aarch64 > *** Failure > *** > https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** > https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/2157/artifac…

1 year

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-19-init-12271-g29189738b832: Failure on aarch64

by Nathan Chancellor

Hi, On Sun, Jun 09, 2024 at 11:37:45PM +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-1233 , 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-allmodconfig after: > > | commit llvmorg-19-init-12271-g29189738b832 > | Author: Dan Liew <dan(a)su-root.co.uk> > | Date: Thu May 23 18:35:24 2024 -0700 > | > | Reland #90786 ([BoundsSafety] Allow 'counted_by' attribute on pointers in structs in C) (#93121) > | > | [BoundsSafety] Reland #93121 Allow 'counted_by' attribute on pointers in structs in C (#93121) > | > | Fixes #92687. > | > | Previously the attribute was only allowed on flexible array members. > | ... 130 lines of the commit log omitted. Thanks a lot for the report. This is expected and how Linux needs to react is still being discussed/figured out: https://github.com/ClangBuiltLinux/linux/issues/2026 https://github.com/ClangBuiltLinux/linux/issues/2027 https://github.com/ClangBuiltLinux/linux/issues/2028 Cheers, Nathan

1 year

1
0
0 0

[Linaro-TCWG-CI] v9.0.0-1299-g1f97715c83: Failure on master-thumb_m0_eabi

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-1249 , please let us know if you are looking at the problem and/or when you have a fix. In arm-eabi cortex-m0 soft after: | commit v9.0.0-1299-g1f97715c83 | Author: Paolo Bonzini <pbonzini(a)redhat.com> | Date: Wed Aug 9 01:10:34 2023 +0200 | | Revert "python: use vendored tomli" | | Now that Ubuntu 20.04 is not included anymore, there is no need to ship | it as part of QEMU; Ubuntu 22.04 includes it and Leap users anyway | need to install all the required dependencies from PyPI. | | This mostly reverts commit ec77ee7634de123b7c899739711000fd21dab68b, | ... 3 lines of the commit log omitted. Results changed to # reset_artifacts: -10 # true: 0 # build_abe binutils: 1 # build_abe stage1 -- --set gcc_override_configure=--disable-multilib --set gcc_override_configure=--with-mode=thumb --set gcc_override_configure=--with-cpu=cortex-m0 --set gcc_override_configure=--with-float=soft: 2 # build_abe newlib: 4 # build_abe stage2 -- --set gcc_override_configure=--disable-multilib --set gcc_override_configure=--with-mode=thumb --set gcc_override_configure=--with-cpu=cortex-m0 --set gcc_override_configure=--with-float=soft: 5 # build_abe gdb: 6 # build_abe qemu: # FAILED From # reset_artifacts: -10 # true: 0 # build_abe binutils: 1 # build_abe stage1 -- --set gcc_override_configure=--disable-multilib --set gcc_override_configure=--with-mode=thumb --set gcc_override_configure=--with-cpu=cortex-m0 --set gcc_override_configure=--with-float=soft: 2 # build_abe newlib: 4 # build_abe stage2 -- --set gcc_override_configure=--disable-multilib --set gcc_override_configure=--with-mode=thumb --set gcc_override_configure=--with-cpu=cortex-m0 --set gcc_override_configure=--with-float=soft: 5 # build_abe gdb: 6 # build_abe qemu: 7 The configuration of this build is: CI config tcwg_gnu_embed_build arm-eabi -mthumb -march=armv6s-m -mtune=cortex-m0 -mfloat-abi=soft -mfpu=auto -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_gnu_embed_build--master-thumb_m0_eabi-build/… Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_build--master-thumb_m0_eabi-build/… Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/qemu/s… Full commit : https://gitlab.com/qemu-project/qemu/commit/1f97715c8390e582f154d8b579c7077… List of configurations that regressed due to this commit : * tcwg_gnu_embed_build ** master-thumb_m0_eabi *** Failure *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/qemu/s… *** https://ci.linaro.org/job/tcwg_gnu_embed_build--master-thumb_m0_eabi-build/…

1 year

1
0
0 0

[ACTIVITY] report week ending 7 Jun

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] - updated our component definition regexes for Coverity Scan - sent patches with the followon cleanup RTH requested when reviewing my FEAT_WFxT patchset - code review - triage of new coverity issues -- PMM

1 year

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-15-1022-gb05288d1f1e: FAIL: 1 regressions on master-thumb_m0_eabi

by Hongtao Liu

Do r15-1050-gfcfce55c85f842ed843cbc4aabe744c6a004dead fix the failure? On Thu, Jun 6, 2024 at 10:06 PM 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-1244 , please let us know if you are looking at the problem and/or when you have a fix. > > In arm-eabi cortex-m0 soft after: > > | commit gcc-15-1022-gb05288d1f1e > | Author: liuhongt <hongtao.liu(a)intel.com> > | Date: Tue May 21 16:57:17 2024 +0800 > | > | Don't simplify NAN/INF or out-of-range constant for FIX/UNSIGNED_FIX. > | > | According to IEEE standard, for conversions from floating point to > | integer. When a NaN or infinite operand cannot be represented in the > | destination format and this cannot otherwise be indicated, the invalid > | operation exception shall be signaled. When a numeric operand would > | convert to an integer outside the range of the destination format, the > | ... 29 lines of the commit log omitted. > > FAIL: 1 regressions > > regressions.sum: > === gcc tests === > > Running gcc:gcc.dg/dg.exp ... > FAIL: gcc.dg/pr100927.c scan-rtl-dump-times final "(?n)\\(fix:SI" 3 > > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu… > The full lists of regressions and progressions as well as configure and make commands are in > - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu… > > The configuration of this build is: > CI config tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv6s-m -mtune=cortex-m0 -mfloat-abi=soft -mfpu=auto > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu… > Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu… > > 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/b05288d1f1e4b632eddf8830b4369d4659… > > List of configurations that regressed due to this commit : > * tcwg_gnu_embed_check_gcc > ** master-thumb_m0_eabi > *** FAIL: 1 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu… -- BR, Hongtao

1 year

1
0
0 0

[Linaro-TCWG-CI] gcc-15-874-g9bda2c4c81b: 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. 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-1242 , please let us know if you are looking at the problem and/or when you have a fix. In CI config tcwg_kernel/gnu-master-arm-stable-allmodconfig after: | commit gcc-15-874-g9bda2c4c81b | Author: David Malcolm <dmalcolm(a)redhat.com> | Date: Tue May 28 15:55:24 2024 -0400 | | libcpp: move label_text to its own header | | No functional change intended. | | libcpp/ChangeLog: | * Makefile.in (TAGS_SOURCES): Add include/label-text.h. | * include/label-text.h: New file. | ... 4 lines of the commit log omitted. Results changed to # reset_artifacts: -10 # build_abe binutils: -9 # build_abe stage1: -5 # build_abe qemu: -2 # linux_n_obj: 33 From # reset_artifacts: -10 # build_abe binutils: -9 # build_abe stage1: -5 # build_abe qemu: -2 # linux_n_obj: 34005 # linux build successful: all # linux boot successful: boot The configuration of this build is: CI config tcwg_kernel/gnu-master-arm-stable-allmodconfig -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-arm-stable-allmodconfig-b… Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-arm-stable-allmodconfig-b… 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/9bda2c4c81b668b1d9abbb58cc4e805ac9… List of configurations that regressed due to this commit : * tcwg_kernel ** gnu-master-arm-stable-allmodconfig *** Failure *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… *** https://ci.linaro.org/job/tcwg_kernel--gnu-master-arm-stable-allmodconfig-b…

1 year

2
1
0 0

Re: [Linaro-TCWG-CI] gcc patch #91570: FAIL: 4 regressions on arm

by Jonathan Wakely

Fixed by v2 of the patch. On Wed, 5 Jun 2024 at 23:18, <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/91570 > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Wed Jun 5 16:31:46 2024 +0100 > | > | libstdc++: Use memchr to optimize std::find [PR88545] > | > | I plan to push this after testing finishes. > | > | -- >8 -- > | > | This optimizes std::find to use memchr when searching for an integer in > | ... 12 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 66fa2f10372 contrib: Fix spelling and capitalization in header-tools > > FAIL: 4 regressions > > regressions.sum: > === libstdc++ tests === > > Running libstdc++:libstdc++-dg/conformance.exp ... > FAIL: std/ranges/adaptors/lazy_split.cc -std=gnu++20 (test for excess errors) > UNRESOLVED: std/ranges/adaptors/lazy_split.cc -std=gnu++20 compilation failed to produce executable > FAIL: std/ranges/adaptors/lazy_split.cc -std=gnu++26 (test for excess errors) > UNRESOLVED: std/ranges/adaptors/lazy_split.cc -std=gnu++26 compilation failed to produce executable > > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/7597/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/7597/artifac… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/7597/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/7597/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2226/artifact/ar… > > 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

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-15-937-g7e322d576eb: FAIL: 8 regressions on aarch64

by Rainer Orth

ci_notify(a)linaro.org writes: > 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-1221 > , 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-15-937-g7e322d576eb > | Author: Rainer Orth <ro(a)CeBiTec.Uni-Bielefeld.DE> > | Date: Fri May 31 09:29:38 2024 +0200 > | > | testsuite: Adjust several dg-additional-files-options calls [PR115294] > | > | A recent patch > | > | commit bdc264a16e327c63d133131a695a202fbbc0a6a0 > | Author: Alexandre Oliva <oliva(a)adacore.com> > | Date: Thu May 30 02:06:48 2024 -0300 > | ... 42 lines of the commit log omitted. > > FAIL: 8 regressions I couldn't find a way to comment on the issue page directly, and I refuse to spend any time on some random CI system du jour. This is a false positive: the previous commit commit bdc264a16e327c63d133131a695a202fbbc0a6a0 Author: Alexandre Oliva <oliva(a)adacore.com> Date: Thu May 30 02:06:48 2024 -0300 broke libgomp testing, hiding any previous failures as described in PR testsuite/115294. My patch restored testing, so all failures previously visible are now visible again. Those failures are well known and tracked as PR testsuite/115140, no regression here.

1 year

2
1
0 0

[Linaro-TCWG-CI] binutils-2_41-release-3303-ga71d8768011: FAIL: 2 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. 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-1225 , please let us know if you are looking at the problem and/or when you have a fix. In master-aarch64 after: | commit binutils-2_41-release-3303-ga71d8768011 | Author: Szabolcs Nagy <szabolcs.nagy(a)arm.com> | Date: Wed Mar 27 15:38:06 2024 +0000 | | aarch64: Add DT_RELR support | | The logic to decide if an input relocation for a symbol becomes a | particular kind of output relocation is one of the hard to maintain | parts of the bfd ld backend, since it is partially repeated across | | elfNN_aarch64_check_relocs (where dynamic relocations are counted per | ... 31 lines of the commit log omitted. FAIL: 2 regressions regressions.sum: === glibc tests === Running glibc:nptl ... FAIL: nptl/tst-pthread-gdb-attach FAIL: nptl/tst-pthread-gdb-attach-static You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-aarch64-build… 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-aarch64-build… The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-aarch64-build… The configuration of this build is: CI config tcwg_gnu_native_check_glibc 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_glibc--master-aarch64-build… Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-aarch64-build… 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=a71d87680110d… List of configurations that regressed due to this commit : * tcwg_gnu_native_check_glibc ** master-aarch64 *** FAIL: 2 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti… *** https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-aarch64-build…

1 year

1
0
0 0

[ACTIVITY] report week ending 31 May

by Peter Maydell

Progress (short week, three days): * UM-2 [QEMU upstream maintainership] - another week of pretty much just code review: + more of RTH's decodetree conversion series (several rounds) + "Connect STM32L4x5 USART devices to the EXTI" v2 + "Check clock connection between STM32L4x5 RCC and peripherals" v3 + fixes to some GICv2 corner case behaviours + move the sbsa-ref default CPU up to Neoverse-N2 + v2 of patchset adding SMP support to xilinx-zynq board model + patch fixing a bug in the error-exit codepath of a virtio-pci function (reported by Coverity) + BCM2835 One-Time-Programmable Memory device emulation + RTH's patchset adding SPARC support to risu + Alex's patches to add a SYS_GET_CMDLINE test to the semihosting-tests + Patch to make ID_AA64ZFR0_EL1 read as 0 when user disables SVE - sent a patch to fix a bug spotted by Coverity in a recent change to the xlnx-dpdma device - multiple target-arm pullreqs -- PMM

1 year, 1 month

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-15-168-g21e7aa5f3ea: FAIL: 6 regressions on aarch64

by Christophe Lyon

Hi Harald, On Mon, 6 May 2024 at 21:02, <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-1214 , please let us know if you are looking at the problem and/or when you have a fix. > > In master-aarch64 after: > > | commit gcc-15-168-g21e7aa5f3ea > | Author: Harald Anlauf <anlauf(a)gmx.de> > | Date: Mon Apr 29 19:52:52 2024 +0200 > | > | Fortran: fix issues with class(*) assignment [PR114827] > | > | gcc/fortran/ChangeLog: > | > | PR fortran/114827 > | * trans-array.cc (gfc_alloc_allocatable_for_assignment): Take into > | account _len of unlimited polymorphic entities when calculating > | ... 9 lines of the commit log omitted. > > FAIL: 6 regressions > > regressions.sum: > === gfortran tests === > > Running gfortran:gfortran.dg/asan/asan.exp ... > FAIL: gfortran.dg/asan/unlimited_polymorphic_34.f90 -fsanitize=address -O0 execution test > FAIL: gfortran.dg/asan/unlimited_polymorphic_34.f90 -fsanitize=address -O1 execution test > FAIL: gfortran.dg/asan/unlimited_polymorphic_34.f90 -fsanitize=address -O2 execution test > FAIL: gfortran.dg/asan/unlimited_polymorphic_34.f90 -fsanitize=address -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test > FAIL: gfortran.dg/asan/unlimited_polymorphic_34.f90 -fsanitize=address -O3 -g execution test > FAIL: gfortran.dg/asan/unlimited_polymorphic_34.f90 -fsanitize=address -Os execution test > > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/14… > The full lists of regressions and progressions as well as configure and make commands are in > - https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/14… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/14… > > The configuration of this build is: > CI config tcwg_gnu_cross_check_gcc master-aarch64 Sorry for the delay in coming back to you regarding this notification. You can consider this as a false alarm, caused by the fact that the above configurations use QEMU, which is not (currently) compatible with LSAN (which is enabled by ASAN). We are working on a fix in our testing framework to avoid such issues in the future. Thanks, Christophe > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/14… > Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/14… > > 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/21e7aa5f3ea44ca2fef8deb8788edffc04… > > List of configurations that regressed due to this commit : > * tcwg_gnu_cross_check_gcc > ** master-aarch64 > *** FAIL: 6 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/14…

1 year, 1 month

1
0
0 0

[ACTIVITY] report week ending 23 May

by Peter Maydell

Progress (short week, three days): * UM-2 [QEMU upstream maintainership] - spent pretty much all week working through the code review backlog that had built up while I was on holiday and at Connect: + RTH's patchset making various updates to the risu random-instruction-sequence tester + a patchset fixing some bugs in our GICv2 emulation + patches adding the cache controller and SMP support to xilinx-zynq + patchset modelling the STM32L4x5 USART interrupt lines properly + Alex's patches to the semihosting tests for SYS_GET_CMDLINE + a patch to fix an assert in the hcd-ohci USB controller if the guest does something silly + reviewed the first half of RTH's 60-patch patchset converting the A64 SIMD decode to decodetree (second half for next week...) -- PMM

1 year, 1 month

1
0
0 0

Fwd: [Linaro-TCWG-CI] gcc patch #89969: Failure on aarch64

by Peter0x44

Hi all, I received this message about my patch failing to build. It probably is my fault, but I cannot figure out why, it bootstraps without problems on my own computer. All of my attempts to reproduce have failed, and I don't have any ideas would could cause this. All of my guesses for fixes haven't worked, and I'm really at the end of my knowledge and ability. Thanks, Peter D. -------- Original Message -------- Subject: [Linaro-TCWG-CI] gcc patch #89969: Failure on aarch64 Date: 2024-05-12 17:14 From: ci_notify(a)linaro.org To: peter0x44(a)disroot.org Reply-To: linaro-toolchain(a)lists.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. In gcc_build master-aarch64 after: | gcc patch https://patchwork.sourceware.org/patch/89969 | Author: Peter Damianov <peter0x44(a)disroot.org> | Date: Sun May 12 06:38:58 2024 -0700 | | driver: Output to a temp file; rename upon success [PR80182] | | Currently, commands like: | gcc -o file.c -lm | will delete the user's code. | | This patch makes the linker write executables to a temp file, and then renames | ... 15 lines of the commit log omitted. | ... applied on top of baseline commit: | 46077992180 arm: Use utxb rN, rM, ror #8 to implement zero_extract on armv6. Results changed to # reset_artifacts: -10 # true: 0 # build_abe gcc: # FAILED # First few build errors in logs: # 00:04:12 make[2]: *** [Makefile:1005: libgcc_s.so] Error 1 # 00:04:12 make[1]: *** [Makefile:14340: all-target-libgcc] Error 2 # 00:04:12 make: *** [Makefile:1062: all] Error 2 From # reset_artifacts: -10 # true: 0 # build_abe gcc: 1 The configuration of this build is: CI config tcwg_gcc_build 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_build--master-aarch64-precommit/8869/art… Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/2030/artifac… 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, 1 month

1
0
0 0

Re: [Linaro-TCWG-CI] gdb-14-branchpoint-2094-gc223d373883: FAIL: 5 regressions on arm

by Christophe Lyon

Hi Pedro, As you may have noticed, this patch caused new failures on arm. Are you working on a fix? Thanks, Christophe On Sat, 13 Apr 2024 at 16:59, <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-1198 , please let us know if you are looking at the problem and/or when you have a fix. > > In gdb_check master-arm after: > > | commit gdb-14-branchpoint-2094-gc223d373883 > | Author: Pedro Alves <pedro(a)palves.net> > | Date: Tue May 2 15:04:28 2023 +0100 > | > | Fix setting watchpoints when current thread is running > | > | Currently, when the current thread is running, you can print global > | variables. However, if you try to set a watchpoint on the same > | globals, GDB errors out, complaining that the selected thread is > | running. Like so: > | > | ... 37 lines of the commit log omitted. > > FAIL: 5 regressions > > regressions.sum: > === gdb tests === > > Running gdb:gdb.base/watchpoint-running.exp ... > FAIL: gdb.base/watchpoint-running.exp: all-stop: hardware: watch global_var > FAIL: gdb.base/watchpoint-running.exp: all-stop: hardware: watchpoint hit (timeout) > FAIL: gdb.base/watchpoint-running.exp: non-stop: hardware: watch global_var > FAIL: gdb.base/watchpoint-running.exp: non-stop: hardware: watchpoint hit (timeout) > > Running gdb:gdb.threads/signal-command-handle-nopass.exp ... > FAIL: gdb.threads/signal-command-handle-nopass.exp: step-over no: signal SIGUSR1 > ... and 1 more entries > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/1050/artifact/ar… > The full lists of regressions and progressions as well as configure and make commands are in > - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/1050/artifact/ar… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/1050/artifact/ar… > > The configuration of this build is: > CI config tcwg_gdb_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_gdb_check--master-arm-build/1050/artifact/ar… > Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/1047/artifact/ar… > > 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=c223d37388320… > > List of configurations that regressed due to this commit : > * tcwg_gdb_check > ** master-arm > *** FAIL: 5 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sh… > *** https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/1050/artifact/ar…

1 year, 1 month

2
1
0 0

[ACTIVITY] report week ending 3 May

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] - last bits of prep and admin for Connect - investigating what we should do with the MPIDR when the user specifies a topology setup when the CPU being emulated is or is not one with MPIDR.MT set. I had written this up as a "bitesized task" in the bug system, but unfortunately it is turning out to be hairier than I had thought at the time... * QEMU-530 [QEMU ARMv9.5 Baseline CPU for TCG] - Finished and sent out patches to implement FEAT_WFxT emulation (WFI/WFE with a timeout) -- PMM

1 year, 1 month

1
0
0 0

RE: [Linaro-TCWG-CI] gcc patch #89057: FAIL: 28 regressions on arm

by Andrew Pinski (QUIC)

These are all expected "failures" for arm (aarch32) really; the new testcases were known to fail for that target; it is recorded as PR 224847. I was not sure how to record this besides in the commit message. Should I xfail them for the targets that are known to fail? Thanks, Andrew Pinski > -----Original Message----- > From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> > Sent: Friday, April 26, 2024 3:15 PM > To: Andrew Pinski (QUIC) <quic_apinski(a)quicinc.com> > Subject: [Linaro-TCWG-CI] gcc patch #89057: FAIL: 28 regressions on arm > > 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/89057 > | Author: Andrew Pinski <quic_apinski(a)quicinc.com> > | Date: Fri Apr 26 10:07:40 2024 -0700 > | > | aarch64: Fix normal returns inside functions which use eh_returns > [PR114843] > | > | The problem here is that on a normal return path, we still restore the > | eh data return when we should not. > | Instead of one return path in the case of eh_return, this changes over > | to use multiple returns pathes just like a normal function. > | On the normal path (non-eh return), we need to skip restoring of the eh > | ... 43 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 6b86f71165d AArch64: Cleanup memset expansion > > FAIL: 28 regressions > > regressions.sum: > === gcc tests === > > Running gcc:gcc.c-torture/execute/execute.exp ... > FAIL: gcc.c-torture/execute/eh_return-1.c -O0 execution test > FAIL: gcc.c-torture/execute/eh_return-1.c -O1 execution test > FAIL: gcc.c-torture/execute/eh_return-1.c -O2 execution test > FAIL: gcc.c-torture/execute/eh_return-1.c -O2 -flto -fno-use-linker-plugin - > flto-partition=none execution test > FAIL: gcc.c-torture/execute/eh_return-1.c -O2 -flto -fuse-linker-plugin -fno- > fat-lto-objects execution test > FAIL: gcc.c-torture/execute/eh_return-1.c -O3 -g execution test > FAIL: gcc.c-torture/execute/eh_return-1.c -Os execution test ... and 22 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/6993/artifact/artifacts/artifacts.precommit/00-sumfiles/ > 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/6993/artifact/artifacts/artifacts.precommit/notify/ > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm- > precommit/6993/artifact/artifacts/artifacts.precommit/sumfiles/xfails.xfail > > 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/6993/artifact/artifacts > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm- > build/2027/artifact/artifacts > > 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
2
0 0

[ACTIVITY] report week ending 26 Apr

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] - made the 9.0 release and handed over pullreq processing to RTH for the 9.1 cycle - collected up and sent out the first target-arm pullreq for 9.1 - finished creating JIRA issues for QEMU for FEAT_* features to bring us into sync with the rev K.a Arm ARM * QEMU-530 [QEMU ARMv9.5 Baseline CPU for TCG] - Sent out v2 of the "make CNTFRQ 1GHz" patchset. This version includes patches to keep sbsa-ref on the old 62.5MHz frequency (since there's no TF-A release yet with the fix to make it not hardcode that value) - Started looking at FEAT_WFxT (WFI/WFE with a timeout) -- PMM

1 year, 2 months

1
0
0 0

gcc patch #88922: FAIL: 1 regressions on aarch64

by Paul Richard Thomas

Hi, Executing on host: /home/tcwg-build/workspace/tcwg_gnu_4/abe/builds/destdir/aarch64-unknown-linux-gnu/bin/aarch64-unknown-linux-gnu-gfortran /home/tcwg-build/workspace/tcwg_gnu_4/abe/snapshots/gcc.git~master/gcc/testsuite/gfortran.dg/pr89462.f90 -fdiagnostics-plain-output -fdiagnostics-plain-output -O -pedantic-errors -S -o pr89462.s (timeout = 600) spawn -ignore SIGHUP /home/tcwg-build/workspace/tcwg_gnu_4/abe/builds/destdir/aarch64-unknown-linux-gnu/bin/aarch64-unknown-linux-gnu-gfortran /home/tcwg-build/workspace/tcwg_gnu_4/abe/snapshots/gcc.git~master/gcc/testsuite/gfortran.dg/pr89462.f90 -fdiagnostics-plain-output -fdiagnostics-plain-output -O -pedantic-errors -S -o pr89462.s /home/tcwg-build/workspace/tcwg_gnu_4/abe/snapshots/gcc.git~master/gcc/testsuite/gfortran.dg/pr89462.f90:6:14: Warning: Obsolescent feature: Old-style character length at (1) /home/tcwg-build/workspace/tcwg_gnu_4/abe/snapshots/gcc.git~master/gcc/testsuite/gfortran.dg/pr89462.f90:7:17: Warning: Obsolescent feature: Old-style character length at (1) As far as I can see, adding -pedantic-errors and the warning fixes the regression. Do you only run the pre-commit regression tests with -pedantic-errors? Thanks Paul

1 year, 2 months

2
1
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain