- linaro-toolchain - lists.linaro.org

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, 4 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, 4 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, 4 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, 4 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, 4 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, 4 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, 5 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, 5 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, 5 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, 5 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, 5 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, 5 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, 5 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, 5 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

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

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

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

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

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

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

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

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

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

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

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

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

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

2
1
0 0

Re: [Linaro-TCWG-CI] 3 patches in gcc: FAIL: 260 regressions on arm

by Qing Zhao

Hi, I am wondering why I got the following message? I only sent patch review request to gcc-patches(a)gcc.gnu.org<mailto:gcc-patches@gcc.gnu.org>, never committed the patches to any public repository. Are there anyone else applied the patches to sourceware and tested them? I have posted many patch review request to gcc-patches(a)gcc.gnu.org<mailto:gcc-patches@gcc.gnu.org>, this is the first time I got such message. Thanks a lot for your help. Qing On Apr 20, 2024, at 00:27, 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: | 3 patches in gcc | Patchwork URL: https://patchwork.sourceware.org/patch/88759 | da63cf36d84 Add testing cases for flexible array members in unions and alone in structures. | 9a83cd642a0 C and C++ FE changes to support flexible array members in unions and alone in structures. | 513291ec443 Documentation change | ... applied on top of baseline commit: | 9f10005dbc9 RISC-V: Add xfail test case for wv insn register overlap FAIL: 260 regressions regressions.sum: === g++ tests === Running g++:g++.dg/dg.exp ... FAIL: c-c++-common/builtin-clear-padding-3.c -std=gnu++14 (test for errors, line 5) FAIL: c-c++-common/builtin-clear-padding-3.c -std=gnu++14 (test for excess errors) FAIL: c-c++-common/builtin-clear-padding-3.c -std=gnu++17 (test for errors, line 5) FAIL: c-c++-common/builtin-clear-padding-3.c -std=gnu++17 (test for excess errors) FAIL: c-c++-common/builtin-clear-padding-3.c -std=gnu++20 (test for errors, line 5) FAIL: c-c++-common/builtin-clear-padding-3.c -std=gnu++20 (test for excess errors) FAIL: c-c++-common/builtin-clear-padding-3.c -std=gnu++98 (test for errors, line 5) ... and 259 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/6897/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/6897/artifac… The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/6897/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/6897/artifac… Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1997/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, 7 months

2
4
0 0

Re: [Linaro-TCWG-CI] gdb-14-branchpoint-2123-g4e417d7bb1c: FAIL: 3 regressions on aarch64

by Christophe Lyon

Hi Tom. As you may have noticed, your patch below caused regressions in the libstdc++ testsuite on aarch64: FAIL: libstdc++-prettyprinters/debug.cc print redirected FAIL: libstdc++-prettyprinters/simple.cc print redirected FAIL: libstdc++-prettyprinters/simple11.cc print redirected For instance, the log contains: $24 = Traceback (most recent call last): File "/home/tcwg-buildslave/workspace/tcwg_gnu_5/abe/snapshots/gcc.git~master/libstdc++-v3/testsuite/../python/libstdcxx/v6/printers.py", line 2279, in to_string got: $24 = Traceback (most recent call last): FAIL: libstdc++-prettyprinters/debug.cc print redirected Do you know if this is a problem in GDB, or if the testcase needs an adjustment like recently for another one? Thanks, Christophe On Thu, 18 Apr 2024 at 01:39, <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-1202 , please let us know if you are looking at the problem and/or when you have a fix. > > In master-aarch64 after: > > | commit gdb-14-branchpoint-2123-g4e417d7bb1c > | Author: Tom Tromey <tom(a)tromey.com> > | Date: Fri Jan 12 18:01:00 2024 -0700 > | > | Change handling of DW_TAG_enumeration_type in DWARF scanner > | > | Currently the DWARF scanner will enter enumeration constants into the > | same namespace as the DW_TAG_enumeration_type itself. This is the > | right thing to do, but the implementation may result in strange > | entries being added to the addrmap that maps DIE ranges to entries. > | > | ... 8 lines of the commit log omitted. > > FAIL: 3 regressions > > regressions.sum: > === libstdc++ tests === > > Running libstdc++:libstdc++-prettyprinters/prettyprinters.exp ... > FAIL: libstdc++-prettyprinters/debug.cc print redirected > FAIL: libstdc++-prettyprinters/simple.cc print redirected > FAIL: libstdc++-prettyprinters/simple11.cc print redirected > > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/1… > The full lists of regressions and progressions as well as configure and make commands are in > - https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/1… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/1… > > The configuration of this build is: > CI config tcwg_gnu_native_check_gcc master-aarch64 > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/1… > Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/1… > > 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=4e417d7bb1c7d… > > List of configurations that regressed due to this commit : > * tcwg_gnu_native_check_gcc > ** master-aarch64 > *** FAIL: 3 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sh… > *** https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/1…

1 year, 7 months

1
0
0 0

[ACTIVITY] report week ending 19 Apr

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] - got rc4 out of the door; 9.0 release next week - working through the rev K.a Arm ARM to resync the list of architecture features we have implemented and the Linaro JIRA issues that track the ones we haven't. Sent a patchset that updates the QEMU documentation to the new feature names and the newly added features that previously were effectively considered part of baseline v8.0. - Sent patches that add some easy "no-op for QEMU" features: FEAT_CSV2_3, FEAT_ETS2, FEAT_Spec_FPACC. - Sorted out the last loose end in the FEAT_NMI patchseries (the cpuif should have a different "NMI supported" state to the IRI), and queued it ready for 9.1 - Queued a few other already-reviewed patchseries ready for 9.1 * QEMU-530 [QEMU ARMv9.5 Baseline CPU for TCG] - Making the generic timer default frequency be 1GHz (required for Arm v8.6 and above). I have patches for this, most of which are concerned with ensuring that for backwards-compatibility we don't use the new default on old CPU types and old versioned machines. -- PMM

1 year, 8 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc patch #88475: Failure on aarch64

by Christophe Lyon

On Mon, 15 Apr 2024 at 12:15, <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_build master-aarch64 after: > > | gcc patch https://patchwork.sourceware.org/patch/88475 > | Author: Fei Gao <gaofei(a)eswincomputing.com> > | Date: Mon Apr 15 06:33:17 2024 +0000 > | > | optimize Zicond conditional select cases. > | > | When one of the two input operands is 0, ADD and IOR are functionally > | equivalent. > | ADD is slightly preferred over IOR because ADD has a higher likelihood > | of being implemented as a compressed instruction when compared to IOR. > | C.ADD uses the CR format with any of the 32 RVI registers availble, > | ... 21 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 7f4ba5480e0 testsuite: i386: Restrict gcc.target/i386/fhardened-1.c etc. to Linux/GNU > > Results changed to > # reset_artifacts: > -10 > # true: > 0 > # build_abe gcc: > # FAILED > # First few build errors in logs: > # 00:11:10 make[2]: *** [/home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/gcc/fortran/Make-lang.in:142: fortran.install-html] Error 1 > # 00:11:10 make[1]: *** [Makefile:5002: install-html-gcc] Error 1 > # 00:11:10 make: *** [Makefile:1895: do-install-html] Error 2 > Please ignore this false alarm: it was caused by a change in our build scripts. The problem should now be fixed. I've manually retriggered the validation, the status should be updated soon in patchwork. Thanks, Christophe > 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/8188/art… > Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/1921/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, 8 months

2
1
0 0

RE: [Linaro-TCWG-CI] 4 patches in gdb: FAIL: 1 regressions: 1 progressions on arm

by Metzger, Markus T

Hello, > | 4 patches in gdb > | Patchwork URL: https://patchwork.sourceware.org/patch/88278 > | 343a2568d2c gdb, infrun: fix multi-threaded reverse stepping > | a4cfc3d32a8 gdb, infrun, record: move no-history notification into >normal_stop > | fc70b453e32 gdb, infrun, record: fix hang when step-over fails with no- >history > | 45548f364fd gdb, infrun, btrace: fix reverse/replay stepping at end of >execution history > | ... applied on top of baseline commit: > | 31c21e2c13d [gdb/testsuite] Fix gdb.threads/access-mem-running-thread- >exit.exp with clang > >FAIL: 1 regressions: 1 progressions > >regressions.sum: > === gdb tests === > >Running gdb:gdb.threads/interrupt-while-step-over.exp ... >FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: >iter=6: wait for stops (timeout) The log contains several FAILs at different iterations, yet this report lists a single new fail at iteration 6 IIUC. Is this test known to be flaky? I tried reproducing this on x86-64 but couldn't find any flakiness with this test. >progressions.sum: > === gdb tests === > >Running gdb:gdb.threads/detach-step-over.exp ... >FAIL: gdb.threads/detach-step-over.exp: breakpoint-condition- >evaluation=host: target-non-stop=on: non-stop=on: displaced=off: >test_detach_command: iter 2: attach (GDB internal error) What is a 'progression'? The log again contains several fails in this test. I also found the same GDB internal error in xfails.xfail on iter 3 instead of 2. I tried reproducing this on x86-64 but couldn't find any flakiness with this test. >You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gdb_check--master-arm- >precommit/2150/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_gdb_check--master-arm- >precommit/2150/artifact/artifacts/artifacts.precommit/notify/ >The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gdb_check--master-arm- >precommit/2150/artifact/artifacts/artifacts.precommit/sumfiles/xfails.xfail > >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- >precommit/2150/artifact/artifacts >Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm- >build/1039/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. If those are indeed real fails introduced by my patches, any chance I can debug this on an x86-64 system? Via simulation, perhaps? thanks, Markus. Intel Deutschland GmbH Registered Address: Am Campeon 10, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de> Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928

1 year, 8 months

2
1
0 0

[ACTIVITY] report week ending Apr 12

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] - looking at some late-breaking patches for various more-or-less 9.0-worthy bugs - tagged rc3; looks like we'll need an rc4, though - back to looking at cleanups and refactorings of our reset handling: + add support for a new reset type RESET_TYPE_SNAPSHOT_LOAD so we can use a new-style reset method for the kind of "load new RNG seed into memory" task we can currently only do with qemu_register_reset_nosnapshotload() or with a Machine reset method + pass the reset type into all reset phase methods, not just 'enter' + experimenting with making Machine a subclass of Device, which should let us clean up some inconsistencies (like Machine having its own reset handling that's different from everything else) -- PMM

1 year, 8 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-14-9891-g5aa3fec38cc: FAIL: 12 regressions on aarch64

by Andre Simoes Dias Vieira

Yeah I'll fix this, looks like a testism due to changes in codegen between dev and commit versions, code improved too so it's the good type of testism ;) ________________________________________ From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Sent: Thursday, April 11, 2024 3:43 PM To: Andre Simoes Dias Vieira Cc: gcc-regression(a)gcc.gnu.org Subject: [Linaro-TCWG-CI] gcc-14-9891-g5aa3fec38cc: FAIL: 12 regressions on aarch64 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-1192 , please let us know if you are looking at the problem and/or when you have a fix. In gcc_check master-aarch64 after: | commit gcc-14-9891-g5aa3fec38cc | Author: Andre Vieira <andre.simoesdiasvieira(a)arm.com> | Date: Wed Apr 10 16:29:46 2024 +0100 | | aarch64: Add support for _BitInt | | This patch adds support for C23's _BitInt for the AArch64 port when compiling | for little endianness. Big Endianness requires further target-agnostic | support and we therefor disable it for now. | | gcc/ChangeLog: | ... 24 lines of the commit log omitted. FAIL: 12 regressions regressions.sum: === gcc tests === Running gcc:gcc.target/aarch64/aarch64.exp ... FAIL: gcc.target/aarch64/bitfield-bitint-abi-align16.c check-function-bodies g1 FAIL: gcc.target/aarch64/bitfield-bitint-abi-align16.c check-function-bodies g16 FAIL: gcc.target/aarch64/bitfield-bitint-abi-align16.c check-function-bodies g16p FAIL: gcc.target/aarch64/bitfield-bitint-abi-align16.c check-function-bodies g1p FAIL: gcc.target/aarch64/bitfield-bitint-abi-align16.c check-function-bodies g8 FAIL: gcc.target/aarch64/bitfield-bitint-abi-align16.c check-function-bodies g8p FAIL: gcc.target/aarch64/bitfield-bitint-abi-align8.c check-function-bodies g1 ... and 6 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/1842/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/1842/artifac… The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1842/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/1842/artifac… Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1841/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/5aa3fec38cc6f52285168b161bab1a869d… List of configurations that regressed due to this commit : * tcwg_gcc_check ** master-aarch64 *** FAIL: 12 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/1842/artifac… IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

1 year, 8 months

1
0
0 0

Re: [Linaro-TCWG-CI] v6.9-rc2-36-gfc4216add64ee: Failure on arm

by Thiago Jung Bauermann

ci_notify(a)linaro.org writes: > In CI config tcwg_kernel/gnu-master-arm-next-allyesconfig after: > > | commit v6.9-rc2-36-gfc4216add64ee > | Author: Samuel Holland <samuel.holland(a)sifive.com> > | Date: Fri Mar 29 00:18:28 2024 -0700 > | > | drm/amd/display: use ARCH_HAS_KERNEL_FPU_SUPPORT > | > | Now that all previously-supported architectures select > | ARCH_HAS_KERNEL_FPU_SUPPORT, this code can depend on that symbol instead > | of the existing list of architectures. It can also take advantage of the > | common kernel-mode FPU API and method of adjusting CFLAGS. > | > | ... 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: > 22511 > > From > # reset_artifacts: > -10 > # build_abe binutils: > -9 > # build_abe stage1: > -5 > # build_abe qemu: > -2 > # linux_n_obj: > 22321 > # linux build successful: > all This problem still reproduces on next-20240410, so I reported it to the patch author. He responded here: https://lore.kernel.org/linux-arm-kernel/75a37a4b-f516-40a3-b6b5-4aa1636f9b… mentioning that it's a shortcoming of GCC on arm: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91970 Though Andrew Pinski has just disagreed with that assessment. -- Thiago

1 year, 8 months

1
0
0 0

Pre-commit execution test for pr113363.f90

by Paul Richard Thomas

Hi there, Thanks for the heads-up on gcc patch #88281: 6 regressions on arm. I see from the log that the test timed-out and the core was dumped. I cannot reproduce this and can see nothing in the tree-dump that might cause a time out. I would appreciate some help on where the fault lies and what the cause might be. Best regards Paul Thomas

1 year, 8 months

3
2
0 0

[ACTIVITY] Report for week #14

by Philippe Mathieu-Daudé

[QEMU maintenance] * Got involved offline via qemu-security@ for 2 bugs for 9.0, sent 2 patches: - virtio dma re-entrancy (use after free) https://lore.kernel.org/qemu-devel/20240404191339.5688-1-philmd@linaro.org/ - hw sdhci (overflow) https://lore.kernel.org/qemu-devel/20240404085549.16987-1-philmd@linaro.org/ * "Misc HW fixes for 9.0" pull request [Single binary] * Still working on sanitizing include/exec/, user emulation part * Analyzed how to merge libtcg system/user code, removing the compile-time uses of CONFIG_SOFTMMU. Left as a peer programming exercise with rth at MAD24 :)

1 year, 8 months

1
0
0 0

[ACTIVITY] report week ending 5 Apr

by Peter Maydell

Progress (short week, 3 days): * UM-2 [QEMU upstream maintainership] - more pullreq wrangling - more FEAT_NMI patchset review: I think I'm now finally done with this - looked at issue #2150 and produced a short standalone repro case from the logfile the user provided (which was from a boot of Windows) -- PMM

1 year, 8 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain