- linaro-toolchain - lists.linaro.org

Re: [Linaro-TCWG-CI] gcc-15-2360-gdab0f35fcb4d: Failure on arm

by Maxim Kuvyrkov

Hi Jason, The regression is ... === g++ tests === Running g++:g++.dg/dg.exp ... FAIL: g++.dg/abi/arm_rtti1.C -std=gnu++26 scan-assembler _ZNKSt9type_infoeqERKS_ It wasn't included in the report due to typo in the scripts. Kind regards, -- Maxim Kuvyrkov https://www.linaro.org > On Jul 28, 2024, at 05:55, 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-1300 , 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-15-2360-gdab0f35fcb4d > | Author: Jason Merrill <jason(a)redhat.com> > | Date: Fri Jul 26 15:10:50 2024 -0400 > | > | c++: improve C++ testsuite default versions > | > | I wanted to add more cases to the setting of std_list in g++-dg.exp, but > | didn't want to do a full scan through the file for each case. So this patch > | improves that in two ways: first, by extracting all interesting lines on a > | single pass; second, by generating the list more flexibly: now we test every > | version mentioned explicitly in the testcase, plus a few more if fewer than > | ... 12 lines of the commit log omitted. > > Results changed to > # reset_artifacts: > -10 > # build_abe gcc: > -2 > # build_abe dejagnu: > -1 > # build_abe check_gcc --: > 0 > # 1 regressions > > From > # reset_artifacts: > -10 > # build_abe gcc: > -2 > # build_abe dejagnu: > -1 > # build_abe check_gcc --: > 0 > > 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/2468/artifact/ar… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2466/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/dab0f35fcb4dd3ba584422013096c4ebc6… > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-arm > *** Failure > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2468/artifact/ar…

1 year, 5 months

1
0
0 0

Re: [Linaro-TCWG-CI] 2 patches in gdb: Failure on aarch64

by Simon Marchi

On 2024-07-27 03:34, 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 gdb_check master-aarch64 after: > > | 2 patches in gdb > | Patchwork URL: https://patchwork.sourceware.org/patch/94605 > | 9aca4cc6ec5 gdb: pass inferior to gdbarch_update_p > | f3b21ad781e gdb: pass inferior to target_current_description > | ... applied on top of baseline commit: > | ced7ecee432 Automatic date update in version.in > > Results changed to > # reset_artifacts: > -10 > # build_abe gdb -- --prefix /usr --disable install: > -2 > # build_abe dejagnu: > -1 > # build_abe check_gdb -- --set check_buffer_workaround=gdb-read1: > 0 > # 1 regressions > > From > # reset_artifacts: > -10 > # build_abe gdb -- --prefix /usr --disable install: > -2 > # build_abe dejagnu: > -1 > # build_abe check_gdb -- --set check_buffer_workaround=gdb-read1: > 0 > > The configuration of this build is: > CI config tcwg_gdb_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_gdb_check--master-aarch64-precommit/2974/art… > Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-aarch64-build/1474/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. Hello, Could you help me understand what failed? Simon

1 year, 5 months

2
1
0 0

Re: [Linaro-TCWG-CI] llvmorg-19-init-18145-g1f6f97e2b64a: Failure on aarch64

by Nathan Chancellor

On Mon, Jul 22, 2024 at 02:12:58PM +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-1287 , 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-stable-allyesconfig after: > > | commit llvmorg-19-init-18145-g1f6f97e2b64a > | Author: Bill Wendling <5993918+bwendling(a)users.noreply.github.com> > | Date: Thu Jul 18 22:11:56 2024 +0000 > | > | [Clang] Loop over FieldDecls instead of all Decls (#99574) > | > | Only FieldDecls are important when determining GEP indices. A struct > | defined within another struct has the same semantics as if it were > | defined outside of the struct. So there's no need to look into > | RecordDecls that aren't a field. > | > | ... 4 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: > 22903 > > From > # reset_artifacts: > -10 > # build_abe binutils: > -9 > # build_kernel_llvm: > -5 > # build_abe qemu: > -2 > # linux_n_obj: > 22904 > > The configuration of this build is: > CI config tcwg_kernel/llvm-master-aarch64-stable-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-stable-allyescon… > Reference build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-stable-allyescon… > > 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/1f6f97e2b64a9c4c51712d32b53e07d… > > List of configurations that regressed due to this commit : > * tcwg_kernel > ** llvm-master-aarch64-stable-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-stable-allyescon… This should be fixed with https://github.com/llvm/llvm-project/commit/6db5f4fd2a287de9d20adc7a44cfcc6…. Cheers, Nathan

1 year, 5 months

1
0
0 0

[Linaro-TCWG-CI] gcc-15-2192-g0c5c0c959c2e: Failure on aarch64

by ci_notify＠linaro.org

Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. 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-1297 , 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-aarch64-mainline-allnoconfig after: | commit gcc-15-2192-g0c5c0c959c2e | Author: Tamar Christina <tamar.christina(a)arm.com> | Date: Mon Jul 22 10:28:19 2024 +0100 | | AArch64: implement TARGET_VECTORIZE_CONDITIONAL_OPERATION_IS_EXPENSIVE [PR115531]. | | This implements the new target hook indicating that for AArch64 when possible | we prefer masked operations for any type vs doing LOAD + SELECT or | SELECT + STORE. | | Thanks, | ... 16 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: 662 From # reset_artifacts: -10 # build_abe binutils: -9 # build_abe stage1: -5 # build_abe qemu: -2 # linux_n_obj: 669 # linux build successful: all # linux boot successful: boot The configuration of this build is: CI config tcwg_kernel/gnu-master-aarch64-mainline-allnoconfig -----------------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-aarch64-mainline-allnocon… Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-mainline-allnocon… 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/0c5c0c959c2e592b84739f19ca771fa69e… List of configurations that regressed due to this commit : * tcwg_kernel ** gnu-master-aarch64-mainline-allnoconfig *** Failure *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… *** https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-mainline-allnocon…

1 year, 5 months

1
0
0 0

[Linaro-TCWG-CI] glibc-2.40.9000-2-g4dc22baa84b: 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-1295 , 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.40.9000-2-g4dc22baa84b | Author: Paul Zimmermann <Paul.Zimmermann(a)inria.fr> | Date: Mon Jul 22 08:54:23 2024 +0200 | | This patch adds larger ulp errors for the log2p1 function. | | Changes in v2: | - added larger error for long double on AMD reported by Adhemerval | (https://sourceware.org/pipermail/libc-alpha/2024-June/157755.html) | | Reviewed-by: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> FAIL: 6 regressions regressions.sum: === glibc tests === Running glibc:math ... FAIL: math/test-double-log2p1 FAIL: math/test-float-log2p1 FAIL: math/test-float32-log2p1 FAIL: math/test-float32x-log2p1 FAIL: math/test-float64-log2p1 FAIL: math/test-ldouble-log2p1 You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1585/artifact/… The full lists of regressions and improvements as well as configure and make commands are in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1585/artifact/… The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1585/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/1585/artifact/… Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1583/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=4dc22baa84bdb4111c0a… 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/1585/artifact/…

1 year, 5 months

1
0
0 0

[Linaro-TCWG-CI] gcc-15-2110-g71b31690a7c5: 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-1294 , 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-next-defconfig after: | commit gcc-15-2110-g71b31690a7c5 | Author: Richard Sandiford <richard.sandiford(a)arm.com> | Date: Wed Jul 17 19:38:11 2024 +0100 | | rtl-ssa: Fix split_clobber_group [PR115928] | | One of the goals of the rtl-ssa representation was to allow a | group of consecutive clobbers to be skipped in constant time, | with amortised sublinear insertion and deletion. This involves | putting consecutive clobbers in groups. Splitting or joining | groups would be linear if we had to update every clobber on | ... 21 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: 0 From # reset_artifacts: -10 # build_abe binutils: -9 # build_abe stage1: -5 # build_abe qemu: -2 # linux_n_obj: 7865 # linux build successful: all # linux boot successful: boot The configuration of this build is: CI config tcwg_kernel/gnu-master-arm-next-defconfig -----------------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-next-defconfig-build/… Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-arm-next-defconfig-build/… 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/71b31690a7c52413496e91bcc5ee4c68af… List of configurations that regressed due to this commit : * tcwg_kernel ** gnu-master-arm-next-defconfig *** Failure *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… *** https://ci.linaro.org/job/tcwg_kernel--gnu-master-arm-next-defconfig-build/…

1 year, 5 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-15-2165-g01c095ab77f8: FAIL: 1 regressions on arm

by Sam James

FAIL: gcc.dg/pr116003.c (test for excess errors) Excess errors: /home/tcwg-buildslave/workspace/tcwg_gnu_5/abe/snapshots/gcc.git~master/gcc/testsuite/gcc.dg/pr116003.c:4:1: sorry, unimplemented: '_BitInt(5)' is not supported on this target /home/tcwg-buildslave/workspace/tcwg_gnu_5/abe/snapshots/gcc.git~master/gcc/testsuite/gcc.dg/pr116003.c:8:1: sorry, unimplemented: '_BitInt(129)' is not supported on this target /home/tcwg-buildslave/workspace/tcwg_gnu_5/abe/snapshots/gcc.git~master/gcc/testsuite/gcc.dg/pr116003.c:11:5: sorry, unimplemented: '_BitInt(128)' is not supported on this target I think it needs dg-do compile { target bitint }.

1 year, 5 months

1
0
0 0

[Linaro-TCWG-CI] gcc-15-2026-g44c9403ed183: Failure on aarch64

by ci_notify＠linaro.org

Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. 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-1282 , 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-aarch64-lts-allmodconfig after: | commit gcc-15-2026-g44c9403ed183 | Author: Alejandro Colomar <alx(a)kernel.org> | Date: Sat Jun 29 15:10:43 2024 +0200 | | c, objc: Add -Wunterminated-string-initialization | | Warn about the following: | | char s[3] = "foo"; | | Initializing a char array with a string literal of the same length as | ... 63 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: 24546 From # reset_artifacts: -10 # build_abe binutils: -9 # build_abe stage1: -5 # build_abe qemu: -2 # linux_n_obj: 24548 The configuration of this build is: CI config tcwg_kernel/gnu-master-aarch64-lts-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-aarch64-lts-allmodconfig-… Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-lts-allmodconfig-… 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/44c9403ed1833ae71a59e84f9e37af3182… List of configurations that regressed due to this commit : * tcwg_kernel ** gnu-master-aarch64-lts-allmodconfig *** Failure *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… *** https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-lts-allmodconfig-…

1 year, 5 months

1
0
0 0

[Linaro-TCWG-CI] gcc patch #93154: FAIL: 1 regressions on arm

by Paul Richard Thomas

Hi there, You detected a failure in gfortran.dg/class_transformational_2.f90: PASS: gfortran.dg/class_transformational_2.f90 -O0 (test for excess errors) PASS: gfortran.dg/class_transformational_2.f90 -O0 execution test PASS: gfortran.dg/class_transformational_2.f90 -O1 (test for excess errors) FAIL: gfortran.dg/class_transformational_2.f90 -O1 execution test PASS: gfortran.dg/class_transformational_2.f90 -O2 (test for excess errors) PASS: gfortran.dg/class_transformational_2.f90 -O2 execution test PASS: gfortran.dg/class_transformational_2.f90 -O3 -fomit-frame-pointer ...snip... PASS: gfortran.dg/class_transformational_2.f90 -O3 -fomit-frame-pointer ...snip... PASS: gfortran.dg/class_transformational_2.f90 -O3 -g (test for excess errors) PASS: gfortran.dg/class_transformational_2.f90 -O3 -g execution test PASS: gfortran.dg/class_transformational_2.f90 -Os (test for excess errors) PASS: gfortran.dg/class_transformational_2.f90 -Os execution test The stop message in the full log indicates a numeric error in the first test. I am unable to reproduce the error. Adding deallocation of all the allocated variables (which I should have done in the first place) and running valgrind with -s shows no errors and no memory loss. I find it odd that it should fail once at -O1 and not at -O2 and higher. Can you provide me with any insights; eg, by rerunning the testcase outside of the dejagnu framework? Thank you for doing this testing, by the way, even if the failure is a bit obscure at the moment. Best regards Paul

1 year, 5 months

2
6
0 0

Re: [Linaro-TCWG-CI] 2 patches in binutils: Failure on arm

by Ulf Samuelsson

I get this problem when the CI is building a patchset for the binutils with my patches. The patchset consists of 7 patches, and I suspect that this error message is generated when only part of the 7 patches are applied. Could this be true? They are interdependent, so there is no way to reorder the patches to make this work if not all the patches are applied. Den 2024-07-07 kl. 02:47, skrev ci_notify(a)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 binutils_build master-arm after: > > | 2 patches in binutils > | Patchwork URL: https://patchwork.sourceware.org/patch/93436 > | dd57e0ed6f6 ldgram.y: Add ASCII parsing > | 304119944bb ldlex.l: Add ASCII token > | ... applied on top of baseline commit: > | 85a67d0a39a Automatic date update in version.in > > Results changed to > # reset_artifacts: > -10 > # true: > 0 > # build_abe binutils: > # FAILED > # First few build errors in logs: > # 00:01:58 /home/tcwg-build/workspace/tcwg_gnu_2/abe/snapshots/binutils.git~master/ld/ldgram.y:711:21: error: too many arguments to function ‘lang_add_string’ > # 00:01:58 /home/tcwg-build/workspace/tcwg_gnu_2/abe/snapshots/binutils.git~master/ld/ldgram.y:717:19: error: too many arguments to function ‘lang_add_string’ > # 00:01:58 make[4]: *** [Makefile:2290: ldgram.o] Error 1 > # 00:01:58 make[3]: *** [Makefile:1903: all-recursive] Error 1 > # 00:01:58 make[2]: *** [Makefile:1092: all] Error 2 > # 00:01:58 make[1]: *** [Makefile:8044: all-ld] Error 2 > # 00:01:58 make: *** [Makefile:1028: all] Error 2 > > From > # reset_artifacts: > -10 > # true: > 0 > # build_abe binutils: > 1 > > The configuration of this build is: > CI config tcwg_binutils_build 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_build--master-arm-precommit/2298/ar… > Reference build : https://ci.linaro.org/job/tcwg_binutils_build--master-arm-build/1304/artifa… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files. -- Best Regards Ulf Samuelsson

1 year, 5 months

2
1
0 0

C++ standard library for build bot clang-armv8-lld-2stage

by mingmingl

Greetings! This is Mingming and I'm an LLVM contributor. I have received a lot of useful code review feedback from aarch64 experts. Thank you for all of that! I'm writing to report a failure ( https://lab.llvm.org/buildbot/#/builders/122/builds/150) on buildbot clang-armv8-lld-2stage triggered by my recent patch. The issue seems to stem from the C++ standard libraries not being configured in the buildbot environment. While using a c-style header is a workaround (which pr 97245 <https://github.com/llvm/llvm-project/pull/97245> did), @petrhosek reminded me that it would be good to inform maintainers so they can take a look, which makes sense to me. Could someone please assist in resolving this configuration problem? Thank you in advance and let me know if I miss anything. Thanks, Mingming

1 year, 5 months

3
4
0 0

[ACTIVITY] report week ending 28 Jun

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] - patch-review queue has filled up again; reviewed at least some patches ready for an arm pullreq - another KVM Forum PC meeting * QEMU-530 [QEMU ARMv9.5 Baseline CPU for TCG] - realized that FEAT_AFP means we need to refactor our FPCR/FPSR implementation, because it adds new AArch64-only bits that aren't visible in the AArch32 FPSCR format. (QEMU for historical reasons implemented FPCR and FPSR as masked views of FPSCR; now we need to switch to having FPSCR be a view of the FPCR/FPSR data.) Wrote the necessary refactoring and sent patchseries out for review. -- PMM

1 year, 6 months

1
0
0 0

Re: [PATCH 1/3] Release structures on function return

by Jørgen Kvalsvik

I think we need to revert this. I got this email from linaro/gcc-regressions: [Linaro-TCWG-CI] gcc-15-1649-g19f630e6ae8d: FAIL: 2 regressions on aarch64 regressions.sum: === gcc tests === Running gcc:gcc.misc-tests/gcov.exp ... FAIL: gcc.misc-tests/gcov-23.c (internal compiler error: in operator[], at vec.h:910) FAIL: gcc.misc-tests/gcov-23.c (test for excess errors) This did not reproduce on my machine, but I took a quick look at the hash-map implementation. hash_map.put calls hash_table.find_slot_with_hash, which calls hash_table.expand, which does move+destroy. auto_vec is not really move-aware which leads to a double-free. The fix is either to make auto_vec move-aware (and more like C++'s std::vector) or revert this patch and apply the original version with an explicit release. OK? Thanks, Jørgen On 6/25/24 12:23, Jan Hubicka wrote: >> The value vec objects are destroyed on exit, but release still needs to >> be called explicitly. >> >> gcc/ChangeLog: >> >> * tree-profile.cc (find_conditions): Release vectors before >> return. > I wonder if you turn > hash_map<int_hash<unsigned, 0>, vec<basic_block>> exprs; > to > hash_map<int_hash<unsigned, 0>, auto_vec<basic_block>> exprs; > Won't hash_map destructor take care of this by itself? > > Honza >> --- >> gcc/tree-profile.cc | 3 +++ >> 1 file changed, 3 insertions(+) >> >> diff --git a/gcc/tree-profile.cc b/gcc/tree-profile.cc >> index e4bb689cef5..18f48e8d04e 100644 >> --- a/gcc/tree-profile.cc >> +++ b/gcc/tree-profile.cc >> @@ -919,6 +919,9 @@ find_conditions (struct function *fn) >> if (!have_post_dom) >> free_dominance_info (fn, CDI_POST_DOMINATORS); >> >> + for (auto expr : exprs) >> + expr.second.release (); >> + >> cov->m_masks.safe_grow_cleared (2 * cov->m_index.last ()); >> const size_t length = cov_length (cov); >> for (size_t i = 0; i != length; i++) >> -- >> 2.39.2 >>

1 year, 6 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-15-1619-g3b9b8d6cfdf5: FAIL: 4 regressions on aarch64

by Surya Kumari Jangala

Hi, I am looking into these regressions. Regards, Surya On 26/06/24 7:51 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. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1270 , 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-1619-g3b9b8d6cfdf5 > | Author: Surya Kumari Jangala <jskumari(a)linux.ibm.com> > | Date: Tue Jun 25 08:37:49 2024 -0500 > | > | ira: Scale save/restore costs of callee save registers with block frequency > | > | In assign_hard_reg(), when computing the costs of the hard registers, the > | cost of saving/restoring a callee-save hard register in prolog/epilog is > | taken into consideration. However, this cost is not scaled with the entry > | block frequency. Without scaling, the cost of saving/restoring is quite > | small and this can result in a callee-save register being chosen by > | ... 14 lines of the commit log omitted. > > FAIL: 4 regressions > > regressions.sum: > === g++ tests === > > Running g++:g++.target/aarch64/sve/acle/aarch64-sve-acle.exp ... > FAIL: gcc.target/aarch64/sve/acle/general/cpy_1.c -march=armv8.2-a+sve -moverride=tune=none check-function-bodies dup_x0_m > === gcc tests === > > Running gcc:gcc.dg/dg.exp ... > FAIL: gcc.dg/pr10474.c scan-rtl-dump pro_and_epilogue "Performing shrink-wrapping" > > Running gcc:gcc.target/aarch64/sve/acle/aarch64-sve-acle.exp ... > ... and 5 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/2235/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/2235/artifac… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2235/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/2235/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2234/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/3b9b8d6cfdf59337f4b7ce10ce92a98044… > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-aarch64 > *** FAIL: 4 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/2235/artifac…

1 year, 6 months

1
0
0 0

[Linaro-TCWG-CI] binutils-2_41-release-3611-g057a2b4c4b5: FAIL: 5 regressions on aarch64

by ci_notify＠linaro.org

Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. 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-1271 , please let us know if you are looking at the problem and/or when you have a fix. In binutils_check master-aarch64 after: | commit binutils-2_41-release-3611-g057a2b4c4b5 | Author: Nick Clifton <nickc(a)redhat.com> | Date: Wed Jun 26 13:17:25 2024 +0100 | | Revert: 35fd2ddeb1d90f1750401cfb6d01fe055656b88d | | PR 20814 FAIL: 5 regressions regressions.sum: === ld tests === Running ld:ld-plugin/libdep.exp ... ERROR: can't read "libdep": no such variable FAIL: libdep test - could not locate libdep plugin ERROR: tcl error sourcing ld-plugin/libdep.exp. ERROR: tcl error code TCL READ VARNAME UNRESOLVED: testcase ld-plugin/libdep.exp' aborted due to Tcl error You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-build/1290/ar… 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-build/1290/ar… The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-build/1290/ar… 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-build/1290/ar… Reference build : https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-build/1288/ar… 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=057a2b4c4b57e… List of configurations that regressed due to this commit : * tcwg_binutils_check ** master-aarch64 *** FAIL: 5 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti… *** https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-build/1290/ar…

1 year, 6 months

1
0
0 0

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, 6 months

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, 6 months

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, 6 months

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, 6 months

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, 6 months

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, 6 months

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, 6 months

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, 6 months

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, 6 months

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, 6 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain