- linaro-toolchain - lists.linaro.org

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] - more code review and pullreq wrangling * QEMU-598 [Model the MPS3-AN536 dual-Cortex-R52 FPGA image] - Wrote code to create the CPUs and the GIC and the UARTs. (Decided in the end not to try to create an a15mpcore-style wrapper device for the CPUs and GIC, because the need to have per-CPU RAM and UARTs makes that a bit awkward.) - Got to a working implementation which can boot the selftest binary and run those parts of the selftest which we expect to work. Also will boot a Linux kernel (support for R52 is not upstream but there are public mailing list patches). - Started on tidying up the patchset and finishing off the loose ends to get it into a state where it can be sent out: hope to be able to do that first half of next week. -- PMM

1 year, 10 months

1
0
0 0

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

by Maxim Kuvyrkov

Hi All, This is a false positive, obviously. We do our best to filter out flaky tests, but in this case "gdb.threads/staticthreads.exp: up 10" PASSed twice in the previous run, and then FAILed twice in the next run. Sneaky! Re. the FAIL, the testcase expects to be " in main .*" after "up 10", but ends up in pthread_join() instead: === up 10 #4 0x0001b864 in pthread_join () (gdb) FAIL: gdb.threads/staticthreads.exp: up 10 === See [1] for details. [1] https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/752/artifact/art… . Hi Thiago, Would you please investigate whether ending up in pthread_join() is expected/reasonable for 32-bit ARM? In other words, whether we have a GDB bug exposed by staticthreads.exp or the testcase needs to be generalized a bit. Thank you, -- Maxim Kuvyrkov https://www.linaro.org > On Jan 31, 2024, at 01:30, 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-1137 , 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-1426-gb960445a459 > | Author: GDB Administrator <gdbadmin(a)sourceware.org> > | Date: Tue Jan 30 00:00:26 2024 +0000 > | > | Automatic date update in version.in > > FAIL: 1 regressions > > regressions.sum: > === gdb tests === > > Running gdb:gdb.threads/staticthreads.exp ... > FAIL: gdb.threads/staticthreads.exp: up 10 > > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/752/artifact/art… > 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/752/artifact/art… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/752/artifact/art… > > 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/752/artifact/art… > Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/751/artifact/art… > > 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=b960445a45981… > > List of configurations that regressed due to this commit : > * tcwg_gdb_check > ** master-arm > *** FAIL: 1 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/752/artifact/art…

1 year, 10 months

2
1
0 0

Re: [Linaro-TCWG-CI] gcc patch #85019: FAIL: 29 regressions on aarch64

by H.J. Lu

On Tue, Jan 30, 2024 at 5:45 PM <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-aarch64 after: > > | gcc patch https://patchwork.sourceware.org/patch/85019 > | Author: H.J. Lu <hjl.tools(a)gmail.com> > | Date: Tue Jan 30 04:56:44 2024 -0800 > | > | Handle private COMDAT function symbol reference in readonly data section > | > | For a private COMDAT function symbol reference in readonly data section, > | instead of putting it in .data.rel.ro or .rodata.cst section, call > | function_rodata_section to get the read-only or relocated read-only > | data section associated with the function DECL so that the COMDAT > | section will be used for the private COMDAT function symbol. > | ... 14 lines of the commit log omitted. > | ... applied on top of baseline commit: > | f2061b2a964 c++: avoid -Wdangling-reference for std::span-like classes [PR110358] > > FAIL: 29 regressions > > regressions.sum: > === gcc tests === > > Running gcc:gcc.c-torture/execute/execute.exp ... > FAIL: gcc.c-torture/execute/pr79286.c -Os (internal compiler error: Segmentation fault) > FAIL: gcc.c-torture/execute/pr79286.c -Os (test for excess errors) > UNRESOLVED: gcc.c-torture/execute/pr79286.c -Os compilation failed to produce executable > > Running gcc:gcc.dg/torture/dg-torture.exp ... > FAIL: gcc.dg/torture/pr67109.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (internal compiler error: Segmentation fault) > FAIL: gcc.dg/torture/pr67109.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess errors) > ... and 25 more entries I can't reproduce it with a cross compiler on x86-64 configured with --target=aarch64-linux But I sent out the v2 patch: https://patchwork.sourceware.org/project/gcc/list/?series=30393 to check decl non-null before dereferencing it. -- H.J.

1 year, 10 months

1
1
0 0

[Linaro-TCWG-CI] glibc-2.38.9000-528-g6bd0e4efcc: FAIL: 1 regressions on arm

by ci_notify＠linaro.org

Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. We track this report status in https://linaro.atlassian.net/browse/GNU-1138 , 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.38.9000-528-g6bd0e4efcc | Author: Arjun Shankar <arjun(a)redhat.com> | Date: Mon Jan 15 17:44:43 2024 +0100 | | syslog: Fix heap buffer overflow in __vsyslog_internal (CVE-2023-6246) | | __vsyslog_internal did not handle a case where printing a SYSLOG_HEADER | containing a long program name failed to update the required buffer | size, leading to the allocation and overflow of a too-small buffer on | the heap. This commit fixes that. It also adds a new regression test | that uses glibc.malloc.check. | ... 4 lines of the commit log omitted. FAIL: 1 regressions regressions.sum: === glibc tests === Running glibc:misc ... FAIL: misc/tst-syslog-long-progname You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/892/artifact/a… 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/892/artifact/a… The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/892/artifact/a… 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/892/artifact/a… Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/890/artifact/a… 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=6bd0e4efcc78f3c0115e… List of configurations that regressed due to this commit : * tcwg_glibc_check ** master-arm *** FAIL: 1 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… *** https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/892/artifact/a…

1 year, 10 months

2
1
0 0

Re: [Linaro-TCWG-CI] binutils patch #84803: FAIL: 1 regressions on arm

by H.J. Lu

This patch has been superseded. On Fri, Jan 26, 2024 at 2:01 PM <ci_notify(a)linaro.org> wrote: > > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > In binutils_check master-arm after: > > | binutils patch https://patchwork.sourceware.org/patch/84803 > | Author: H.J. Lu <hjl.tools(a)gmail.com> > | Date: Fri Jan 26 10:09:48 2024 -0800 > | > | ld: Turn on --error-execstack/--error-rwx-segments > | > | Since --fatal-warnings always turns a warning to an error, turn on > | --error-execstack for --warn-execstack and --error-rwx-segments for > | --warn-rwx-segments if --fatal-warnings is used, overriding > | --no-error-execstack and --no-error-rwx-segments. > | > | ... 8 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 91cdbed4d7b gas: scfi: untraceable control flow should be a hard error > > FAIL: 1 regressions > > regressions.sum: > === ld tests === > > Running ld:ld-elf/elf.exp ... > FAIL: PR ld/31299 (error about absent .note.GNU-stack) > > === Results Summary === > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_binutils_check--master-arm-precommit/1003/ar… . > The full lists of regressions and progressions are in > - https://ci.linaro.org/job/tcwg_binutils_check--master-arm-precommit/1003/ar… . > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_binutils_check--master-arm-precommit/1003/ar… . > > The configuration of this build is: > CI config tcwg_binutils_check master-arm > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_binutils_check--master-arm-precommit/1003/ar… > Reference build : https://ci.linaro.org/job/tcwg_binutils_check--master-arm-build/696/artifac… -- H.J.

1 year, 10 months

1
0
0 0

[ACTIVITY] report week ending 26 Jan

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] - Respin of a series I wrote back in Autumn to properly wire up the NS EL2 timer IRQ on the virt board. The delay was because the change tickles a bug in EDK2 that makes it assert on bootup; but now we have updated EDK2 binaries in QEMU we can put in the QEMU change. - Code review: + a patchset adding support for building on GNU Hurd + v2 of an imx serial device patch + add PCI controller to imx6 board - Minor patches sent: + fix a portability bug in our const_le64() macro + fix a regression in SQSHRN/SQRSHRN + fix a bug caused by a typo in our TICDP1 feature-detect function + my version of a patch fixing mishandling of '-serial none' option + Add ID_AA64ZFR0_EL1.B16B16 to the exposed-to-userspace set when we're in user-emulation mode + Clean up some #include lines using scripts/clean-includes + Remove last VLA use in the tree and enable -Wvla warning - Some gardening of the "bite-sized tasks" wiki page: remove a few tasks that are actually complete, write up a better description for one in the bug tracker, and add some notes for another. * QEMU-598 [Model the MPS3-AN536 dual-Cortex-R52 FPGA image] - wrote some patches to add most of the devices to the board model. The main missing ones are the UARTs, which are a little more complicated because a couple of them are per-CPU rather than shared between all CPUs. thanks -- PMM

1 year, 10 months

1
0
0 0

Re: [Linaro-TCWG-CI] binutils patch #84755: FAIL: 2 regressions on aarch64

by H.J. Lu

On Thu, Jan 25, 2024 at 8:06 PM <ci_notify(a)linaro.org> wrote: > > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > In binutils_check master-aarch64 after: > > | binutils patch https://patchwork.sourceware.org/patch/84755 > | Author: H.J. Lu <hjl.tools(a)gmail.com> > | Date: Thu Jan 25 12:11:02 2024 -0800 > | > | bfd: Output error for linker --fatal-warnings option > | > | Update _bfd_error_handler to output the warning prefix, which is default > | to "warning". Add %%w to _bfd_doprnt to output "error", instead of > | "warning", when --fatal-warnings is used. Update bfd_set_error_handler > | to allow linker to set the warning prefix to "error" for --fatal-warnings. > | > | ... 132 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 8409b75c8db Automatic date update in version.in > > FAIL: 2 regressions > > regressions.sum: > === ld tests === > > Running ld:ld-elf/elf.exp ... > FAIL: ld-elf/fatal-warnings-5 > > Running ld:ld-scripts/defined.exp ... > FAIL: ld-scripts/defined7 Although this patch: https://patchwork.sourceware.org/project/binutils/list/?series=30216 can be applied independently, this requires: https://patchwork.sourceware.org/project/binutils/list/?series=30210 > === Results Summary === > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/983… . > The full lists of regressions and progressions are in > - https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/983… . > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/983… . > > The configuration of this build is: > CI config tcwg_binutils_check master-aarch64 > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/983… > Reference build : https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-build/690/art… -- H.J.

1 year, 10 months

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-19-init-59-g90ba33099cbb: Failure on aarch64

by Nathan Chancellor

On Thu, Jan 25, 2024 at 08:20:54PM +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-1105 , 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-59-g90ba33099cbb > | Author: Nikita Popov <npopov(a)redhat.com> > | Date: Wed Jan 24 15:25:29 2024 +0100 > | > | [InstCombine] Canonicalize constant GEPs to i8 source element type (#68882) > | > | This patch canonicalizes getelementptr instructions with constant > | indices to use the `i8` source element type. This makes it easier for > | optimizations to recognize that two GEPs are identical, because they > | don't need to see past many different ways to express the same offset. > | > | ... 14 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: > 22291 > # First few build errors in logs: > > # 00:05:24 ./include/linux/fortify-string.h:493:4: error: call to '__write_overflow_field' declared with 'warning' attribute: detected write beyond size of field (1st parameter); maybe use struct_group()? [-Werror,-Wattribute-warning] > # 00:05:25 make[4]: *** [scripts/Makefile.build:243: net/xfrm/xfrm_user.o] Error 1 > # 00:05:32 make[3]: *** [scripts/Makefile.build:480: net/xfrm] Error 2 This one is the new warning tied to the above LLVM change, I filed https://github.com/ClangBuiltLinux/linux/issues/1985 for that a little bit ago. > # 00:15:32 ./include/linux/fortify-string.h:493:4: error: call to '__write_overflow_field' declared with 'warning' attribute: detected write beyond size of field (1st parameter); maybe use struct_group()? [-Werror,-Wattribute-warning] > # 00:15:32 make[5]: *** [scripts/Makefile.build:243: fs/smb/client/cifsencrypt.o] Error 1 This one is https://github.com/ClangBuiltLinux/linux/issues/1966. Cheers, Nathan

1 year, 10 months

1
0
0 0

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

by Maxim Kuvyrkov

> On Jan 25, 2024, at 04:08, 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-1120 , 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-1354-g8669a8b6740 > | Author: Guinevere Larsen <blarsen(a)redhat.com> > | Date: Thu Aug 24 11:00:35 2023 +0200 > | > | gdb/testsuite: add test for backtracing for threaded inferiors from a corefile > | > | This patch is based on an out-of-tree patch that fedora has been > | carrying for a while. It tests if GDB is able to properly unwind a > | threaded program in the following situations: > | * regular threads > | * in a signal handler > | ... 14 lines of the commit log omitted. > > FAIL: 2 regressions > > regressions.sum: > === gdb tests === > > Running gdb:gdb.threads/threadcrash.exp ... > FAIL: gdb.threads/threadcrash.exp: test_gcore: $thread_count == 7 > FAIL: gdb.threads/threadcrash.exp: test_gcore: $thread_count == [llength $test_list] Hi Guinevere, The failures seem to be due to "LWP" output (instead of "Thread") in test_gcore. I.e., test_corefile succeeds with === (gdb) PASS: gdb.threads/threadcrash.exp: test_corefile: loading_corefile info threads Id Target Id Frame * 1 Thread 0xf7dbe7e0 (LWP 476389) 0x00830cea in crash_function () at /home/tcwg-buildslave/workspace/tcwg_gnu_4/abe/snapshots/gdb.git~master/gdb/testsuite/gdb.threads/threadcrash.c:381 2 Thread 0xf7c6f3a0 (LWP 476390) do_spin_task (location=NORMAL) at /home/tcwg-buildslave/workspace/tcwg_gnu_4/abe/snapshots/gdb.git~master/gdb/testsuite/gdb.threads/threadcrash.c:139 3 Thread 0xf746e3a0 (LWP 476391) do_spin_task (location=SIGNAL_HANDLER) at /home/tcwg-buildslave/workspace/tcwg_gnu_4/abe/snapshots/gdb.git~master/gdb/testsuite/gdb.threads/threadcrash.c:139 4 Thread 0xf6c6d3a0 (LWP 476392) do_spin_task (location=SIGNAL_ALT_STACK) at /home/tcwg-buildslave/workspace/tcwg_gnu_4/abe/snapshots/gdb.git~master/gdb/testsuite/gdb.threads/threadcrash.c:139 5 Thread 0xf52fe3a0 (LWP 476395) __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:46 6 Thread 0xf646c3a0 (LWP 476393) __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:46 7 Thread 0xf5aff3a0 (LWP 476394) __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:46 (gdb) PASS: gdb.threads/threadcrash.exp: test_corefile: $thread_count == 7 === and then test_gcore fails with === (gdb) PASS: gdb.threads/threadcrash.exp: test_gcore: loading_corefile info threads Id Target Id Frame * 1 LWP 476440 0x00400cea in crash_function () at /home/tcwg-buildslave/workspace/tcwg_gnu_4/abe/snapshots/gdb.git~master/gdb/testsuite/gdb.threads/threadcrash.c:381 2 LWP 476442 do_spin_task (location=NORMAL) at /home/tcwg-buildslave/workspace/tcwg_gnu_4/abe/snapshots/gdb.git~master/gdb/testsuite/gdb.threads/threadcrash.c:139 3 LWP 476443 do_spin_task (location=SIGNAL_HANDLER) at /home/tcwg-buildslave/workspace/tcwg_gnu_4/abe/snapshots/gdb.git~master/gdb/testsuite/gdb.threads/threadcrash.c:139 4 LWP 476444 do_spin_task (location=SIGNAL_ALT_STACK) at /home/tcwg-buildslave/workspace/tcwg_gnu_4/abe/snapshots/gdb.git~master/gdb/testsuite/gdb.threads/threadcrash.c:139 5 LWP 476445 0xf7eadb04 in ?? () 6 LWP 476446 0xf7eadb04 in ?? () 7 LWP 476447 0xf7eadb04 in ?? () (gdb) FAIL: gdb.threads/threadcrash.exp: test_gcore: $thread_count == 7 === Could you please look into fixing the testcase? [I assume "LWP" output is expected, but I'm not an expert in GDB.] Thanks! -- Maxim Kuvyrkov https://www.linaro.org > > === Results Summary === > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/726/artifact/art… . > The full lists of regressions and progressions are in > - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/726/artifact/art… . > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/726/artifact/art… . > > 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/726/artifact/art… > Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/724/artifact/art… > > 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=8669a8b67408c… > > List of configurations that regressed due to this commit : > * tcwg_gdb_check > ** master-arm > *** FAIL: 2 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/726/artifact/art…

1 year, 10 months

2
3
0 0

[ACTIVITY] report week ending Jan 19

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] - patch review: + v4 of the raspi-4 SoC/board model series (this is a big one) + bug in calculation of limit address in designware pci controller model + imx7 serial device: implementation of FIFO and ageing timer + patchset to reduce size of fdt blob - started looking at some of my old device/bus reset cleanup patches, since another dev on-list was running into a potential issue that they might help to solve. Failed to repro the test failure that was the reason I put them on the back burner, so sent them out to the list as-is... * QEMU-598 [Model the MPS3-AN536 dual-Cortex-R52 FPGA image] - updated the SCC device to handle the AN536 specifics (most actual behaviour will be unimplemented, as we do for our other board models that have this device) - checked that we don't need to make any changes to the ioregs device; the existing model is flexible enough we can configure it to match the AN536 specifics - wrote the initial skeleton of the board model (which only creates the RAM and ROM regions for the moment) - realized that it might be better to wait for Philippe's reworking of hw/cpu/a15mpcore.c and friends before adding another similar object for the Cortex-R52 thanks -- PMM

1 year, 10 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc patch #83662: FAIL: 8 regressions on arm

by Maxim Kuvyrkov

Hi H.J., Did the email below made it to your inbox? I wonder if some of our precommit CI emails are not reaching developers. Kind regards, -- Maxim Kuvyrkov https://www.linaro.org > On Jan 10, 2024, at 02:24, ci_notify(a)linaro.org wrote: > > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > In gcc_check master-arm after: > > | gcc patch https://patchwork.sourceware.org/patch/83662 > | Author: H.J. Lu <hjl.tools(a)gmail.com> > | Date: Tue Jan 9 08:46:59 2024 -0800 > | > | hwasan: Check if Intel LAM_U57 is enabled > | > | When -fsanitize=hwaddress is used, libhwasan will try to enable LAM_U57 > | in the startup code. Update the target check to enable hwaddress tests > | if LAM_U57 is enabled. Also compile hwaddress tests with -mlam=u57 on > | x86-64 since hwasan requires LAM_U57 on x86-64. > | > | ... 3 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 9f7afa99c67 [committed] Adding missing prototype for __clzhi2 to xstormy port > > FAIL: 8 regressions > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/hwasan/hwasan.exp ... > ERROR: can't read "target_hwasan_flags": no such variable > ERROR: tcl error code TCL LOOKUP VARNAME target_hwasan_flags > ERROR: tcl error sourcing g++.dg/hwasan/hwasan.exp. > UNRESOLVED: testcase g++.dg/hwasan/hwasan.exp' aborted due to Tcl error > === gcc tests === > > Running gcc:gcc.dg/hwasan/hwasan.exp ... > ... 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-arm-precommit/5612/artifac… . > The full lists of regressions and progressions are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/5612/artifac… . > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/5612/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/5612/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1542/artifact/ar…

1 year, 10 months

2
3
0 0

Re: [Linaro-TCWG-CI] gcc-14-8168-g14338386970: FAIL: 3 regressions on arm

by Nathaniel Shead

Thanks for the notification! I took a look and the error seems to be something specific to the TLS implementation for ARM requiring additional flags to link correctly, maybe? I'm unable to test locally (I don't have access to an ARM machine) but from looking at other testsuite examples which make use of thread locals, adding the following two lines to the testcases may resolve the failures: // { dg-add-options tls } // { dg-require-effective-target tls_runtime } Please let me know if the issue is something else and I can take another look. Yours, Nathaniel. On Thu, Jan 18, 2024 at 07:12:12AM +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-1112 , please let us know if you are looking at the problem and/or when you have a fix. > > In master-arm_eabi after: > > | commit gcc-14-8168-g14338386970 > | Author: Nathaniel Shead <nathanieloshead(a)gmail.com> > | Date: Thu Jan 11 16:49:39 2024 +1100 > | > | c++: Support thread_local statics in header modules [PR113292] > | > | Currently, thread_locals in header modules cause ICEs. This patch makes > | the required changes for them to work successfully. > | > | This requires additionally writing the DECL_TLS_MODEL for thread-local > | variables to the module interface, and the TLS wrapper function needs to > | ... 24 lines of the commit log omitted. > > FAIL: 3 regressions > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/modules/modules.exp ... > FAIL: g++.dg/modules/pr113292 -std=c++17 link > FAIL: g++.dg/modules/pr113292 -std=c++2a link > FAIL: g++.dg/modules/pr113292 -std=c++2b link > > === Results Summary === > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/5… . > The full lists of regressions and progressions are in > - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/5… . > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/5… . > > The configuration of this build is: > CI config tcwg_gnu_embed_check_gcc master-arm_eabi > > -----------------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_eabi-build/5… > Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/5… > > 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/14338386970bc6c2d46b81181f48622fdf… > > List of configurations that regressed due to this commit : > * tcwg_gnu_embed_check_gcc > ** master-arm_eabi > *** FAIL: 3 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-arm_eabi-build/5…

1 year, 10 months

2
1
0 0

[Linaro-TCWG-CI] glibc-2.38.9000-496-gdf11c05be9: FAIL: 1 regressions on arm

by ci_notify＠linaro.org

Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. We track this report status in https://linaro.atlassian.net/browse/GNU-1111 , please let us know if you are looking at the problem and/or when you have a fix. In master-arm after: | commit glibc-2.38.9000-496-gdf11c05be9 | Author: Joseph Myers <josmyers(a)redhat.com> | Date: Wed Jan 17 15:38:54 2024 +0000 | | Update syscall lists for Linux 6.7 | | Linux 6.7 adds the futex_requeue, futex_wait and futex_wake syscalls, | and enables map_shadow_stack for architectures previously missing it. | Update syscall-names.list and regenerate the arch-syscall.h headers | with build-many-glibcs.py update-syscalls. | | ... 1 lines of the commit log omitted. FAIL: 1 regressions regressions.sum: === glibc tests === Running glibc:misc ... FAIL: misc/tst-glibcsyscalls === Results Summary === You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/559… . The full lists of regressions and progressions are in - https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/559… . The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/559… . The configuration of this build is: CI config tcwg_gnu_native_check_glibc master-arm -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/559… Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/558… 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=df11c05be91fda5ef490… List of configurations that regressed due to this commit : * tcwg_gnu_native_check_glibc ** master-arm *** FAIL: 1 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… *** https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/559…

1 year, 10 months

3
2
0 0

Re: [Linaro-TCWG-CI] gdb-14-branchpoint-1244-gfad00902c24: FAIL: 13 regressions: 13 progressions on arm

by Thiago Jung Bauermann

Hello Nick, ci_notify(a)linaro.org writes: > In gdb_check master-arm after: > > | commit gdb-14-branchpoint-1244-gfad00902c24 > | Author: Nick Clifton <nickc(a)redhat.com> > | Date: Mon Jan 15 12:25:00 2024 +0000 > | > | nm: Replace --with-symbol-versions with --without-symbol-versions in --help output > | > | PR 31243 > | nm: Fix --help output > > FAIL: 13 regressions: 13 progressions > > regressions.sum: > === gdb tests === > > Running gdb:gdb.mi/mi-var-invalidate.exp ... > ERROR: : spawn id exp8 not open > ERROR: Couldn't send -var-info-type global_simple to GDB. > ERROR: Couldn't send -var-info-type linteger to GDB. > ERROR: Couldn't send -var-update global_simple to GDB. > ERROR: Couldn't send -var-update linteger to GDB. > ERROR: Process no longer exists > ERROR: couldn't load outputs/gdb.mi/mi-var-invalidate/basics into ../../gdb/gdb (end of file). > ... and 8 more entries As you're aware, the above are flaky results that the CI wasn't able to filter out as it normally does. Sorry for the false positive. -- Thiago

1 year, 10 months

2
1
0 0

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

by Tom de Vries

On 1/16/24 07:42, ci_notify(a)linaro.org wrote: > FAIL: 1 regressions: 1 progressions > > regressions.sum: > === gdb tests === > > Running gdb:gdb.threads/staticthreads.exp ... > FAIL: gdb.threads/staticthreads.exp: up 10 FTR, filed as https://sourceware.org/bugzilla/show_bug.cgi?id=31254 . Thanks, - Tom

1 year, 10 months

1
0
0 0

Re: [Linaro-TCWG-CI] 5 patches in gdb: FAIL: 121 regressions: 1 progressions on arm

by Thiago Jung Bauermann

Hello, ci_notify(a)linaro.org writes: > In gdb_check master-arm after: > > | 5 patches in gdb > | Patchwork URL: https://patchwork.sourceware.org/patch/84201 > | 4a7c4c70418 Added docs > | e50ecf9d8ee Add breakpointLocations request > | 74f628035c8 Change gdb.LineTableEntry & Add gdb.lookup_linetable > | a7dd827cb3a Add column to maint info linetable output > | 013518443b6 Add column to linetable entry > | ... applied on top of baseline commit: > | 87339680236 Automatic date update in version.in > > FAIL: 121 regressions: 1 progressions > > regressions.sum: > === gdb tests === > > Running gdb:gdb.base/async.exp ... > FAIL: gdb.base/async.exp: finish& > FAIL: gdb.base/async.exp: nexti& > > Running gdb:gdb.base/maint.exp ... > UNRESOLVED: gdb.base/maint.exp: help maint > UNRESOLVED: gdb.base/maint.exp: help maint info > UNRESOLVED: gdb.base/maint.exp: help maint print > ... and 172 more entries The Linaro CI is undergoing some instability. These failures aren't related to your patch. Sorry for the false alarm. -- Thiago

1 year, 10 months

1
0
0 0

some help with reproducing a ci fail

by Iain Sandoe

Hi So, I have a ci fail email, and it seems likely to be a valid complaint - but the reproduce instructions do not work on my platform (bash is not new enough) and also do not work on cfarm186 (../jenkins-scripts/jenkins-helpers.sh: line 1762: ts: command not found) For the record, the patch that is flagged as failing *was* tested on aarch64-linux-gnu (cfarm185) So, I am trying to figure out if the target is different, or some other configure argument. .. but I cannot work out the failing configure line at present - nor can I see a place to download the console log from the actual failing GCC build (which would presumably have that configure line). any help much appreciated. Iain

1 year, 11 months

2
2
0 0

Re: [Linaro-TCWG-CI] 7 patches in gcc: Failure on arm

by Lehua Ding

Hi, I received an error reported by CI for my patchs, I would like to ask how I have to reproduce it locally? I looked at the logs and didn't find the way how it compiles. Thanks in advance. On 2023/11/8 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. > > In gcc_build master-arm after: > > | 7 patches in gcc > | Patchwork URL: https://patchwork.sourceware.org/patch/79366 > | ef64c12c9f0 lra: Support subreg live range track and conflict detect > | a871f544e2b lra: Apply live_subreg df_problem to lra pass > | 6437747d6f3 ira: Add all nregs >= 2 pseudos to tracke subreg list > | 1a2da1ad5f0 ira: Support subreg copy > | 4f8d8e764e0 ira: Support subreg live range track > | ... and 2 more patches in gcc > | ... applied on top of baseline commit: > | ca281a7b971 [i386] APX: Fix ICE due to movti postreload splitter [PR112394] > > Results changed to > # reset_artifacts: > -10 > # true: > 0 > # build_abe gcc: > # FAILED > # First few build errors in logs: > # 00:03:49 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/libgcc2.c:2700:1: internal compiler error: Aborted > # 00:03:49 make[2]: *** [Makefile:505: _muldc3.o] Error 1 > # 00:03:49 make[1]: *** [Makefile:14486: all-target-libgcc] Error 2 > # 00:03:49 make: *** [Makefile:1056: all] Error 2 > # 00:03:41 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/fixed-bit.c:72:1: internal compiler error: Aborted > # 00:03:41 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/libgcc2.c:2700:1: internal compiler error: Aborted > # 00:03:41 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/fixed-bit.c:72:1: internal compiler error: Aborted > # 00:03:41 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/fixed-bit.c:72:1: internal compiler error: Aborted > # 00:03:41 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/fixed-bit.c:72:1: internal compiler error: Aborted > # 00:03:42 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/libgcc2.c:2865:1: internal compiler error: Aborted > # 00:03:42 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/fixed-bit.c:143:1: internal compiler error: Aborted > # 00:03:42 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/fixed-bit.c:143:1: internal compiler error: Aborted > # 00:03:42 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/fixed-bit.c:143:1: internal compiler error: Aborted > # 00:03:42 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/fixed-bit.c:143:1: internal compiler error: Aborted > > From > # reset_artifacts: > -10 > # true: > 0 > # build_abe gcc: > 1 > > The configuration of this build is: > CI config tcwg_gcc_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_gcc_build--master-arm-precommit/4076/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-arm-build/1364/artifact/ar… -- Best, Lehua (RiVAI) lehua.ding(a)rivai.ai

1 year, 11 months

2
1
0 0

Re: [Linaro-TCWG-CI] gcc patch #80969: Failure on arm

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. > > In gcc_build master-arm after: > > | gcc patch https://patchwork.sourceware.org/patch/80969 > | Author: Rainer Orth <ro(a)CeBiTec.Uni-Bielefeld.DE> > | Date: Wed Nov 29 15:10:00 2023 +0100 > | > | libiberty: Disable hwcaps for sha1.o > | > | This patch > | > | commit bf4f40cc3195eb7b900bf5535cdba1ee51fdbb8e > | Author: Jakub Jelinek <jakub(a)redhat.com> > | Date: Tue Nov 28 13:14:05 2023 +0100 > | ... 26 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 4c909c6ee38 In 'libgomp.c/target-simd-clone-{1,2,3}.c', restrict > | 'scan-offload-ipa-dump's to 'only_for_offload_target amdgcn-amdhsa' > > Results changed to > # reset_artifacts: > -10 > # true: > 0 > # build_abe gcc: > # FAILED > # First few build errors in logs: > # 00:02:15 gccgo: fatal error: Killed signal terminated program go1 > # 00:02:23 gcc: error: @HWCAP_CFLAGS@: linker input file not found: No such > file or directory > # 00:02:23 make[2]: *** [Makefile:1219: regex.o] Error 1 > # 00:02:23 make[1]: *** [Makefile:8370: all-libiberty] Error 2 > # 00:02:23 make: *** [Makefile:1057: all] Error 2 > # 00:01:06 gccgo: fatal error: Killed signal terminated program go1 > # 00:02:10 gcc: error: @HWCAP_CFLAGS@: linker input file not found: No such > file or directory > # 00:02:10 make[2]: *** [Makefile:776: fdmatch.o] Error 1 > # 00:02:10 gcc: error: @HWCAP_CFLAGS@: linker input file not found: No such > file or directory > # 00:02:10 make[2]: *** [Makefile:805: filedescriptor.o] Error 1 > # 00:02:10 gcc: error: @HWCAP_CFLAGS@: linker input file not found: No such > file or directory > # 00:02:10 make[2]: *** [Makefile:837: fnmatch.o] Error 1 > # 00:02:10 gcc: error: @HWCAP_CFLAGS@: linker input file not found: No such > file or directory > # 00:02:10 make[2]: *** [Makefile:817: filename_cmp.o] Error 1 > # 00:02:10 gcc: error: @HWCAP_CFLAGS@: linker input file not found: No such > file or directory > > From > # reset_artifacts: > -10 > # true: > 0 > # build_abe gcc: > 1 > > The configuration of this build is: > CI config tcwg_gcc_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_gcc_build--master-arm-precommit/4887/artifac… > Reference build : > https://ci.linaro.org/job/tcwg_gcc_build--master-arm-build/1444/artifact/ar… > As is customary for gcc patches, this patch didn't include the generated files to simplify review. Thus, to test it in any meaningful way, one needs to run aclocal and autoconf before configuring/building. Not doing so just produces meaningless mails from the CI. Rainer

1 year, 11 months

2
1
0 0

[ACTIVITY] report week ending 12 Jan

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] - further diagnosed the cause of the reported regression in virtio-pci running Linux on 32-bit arm emulation: the kernel the user was using was a non-LPAE one. So the fix is "use an LPAE kernel, or else manually set highmem=off". It would be nice if the kernel produced a more helpful error message for the case where it was built without CONFIG_LPAE and the PCI controller ECAM window is above the 4GB mark... - lots of code review this week, including: + a patch trying to add support to the memory system core for unaligned accesses to a device whose implementation doesn't directly handle them itself + another round of the Nuvoton GMAC and Mailbox device patchset + various parts of the new STM32L4x5 emulation + other smaller patches - patch: remove some now-unneeded code from arm_pamax() - patch: improve docs for the virt board 'highmem' option - patch: work around a bug in 'htags' that was causing intermittent failures of one of our CI jobs - patch: fix 'raven' PCI controller handling of unaligned accesses - handling merging of pull requests; spent some time making sure we have reported issues in our bug tracker (new tag "flaky-ci") for any intermittent CI failures, and asking people to investigate some of them -- PMM

1 year, 11 months

1
0
0 0

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

by Christophe Lyon

Hi, I guess this is a false alarm since the error message was FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6110) and is now: FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6112) (that is, only the line number changes) Thanks, Christophe On Thu, 11 Jan 2024 at 08:32, <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-1101 , please let us know if you are looking at the problem and/or when you have a fix. > > In master-aarch64 after: > > | commit gcc-14-7074-gf9fbf93dc82 > | Author: waffl3x <waffl3x(a)protonmail.com> > | Date: Sun Jan 7 00:00:10 2024 +0000 > | > | c++: P0847R7 (deducing this) - prerequisite changes. [PR102609] > | > | Adds the xobj_flag member to lang_decl_fn and a corresponding member access > | macro and predicate to support the addition of explicit object member > | functions. Additionally, since explicit object member functions are also > | non-static member functions, we need to change uses of > | DECL_NONSTATIC_MEMBER_FUNCTION_P to clarify whether they intend to include > | ... 76 lines of the commit log omitted. > > FAIL: 15 regressions: 15 progressions > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/modules/modules.exp ... > FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6112) > FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2a (internal compiler error: in core_vals, at cp/module.cc:6112) > FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6112) > FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6112) > FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2a (internal compiler error: in core_vals, at cp/module.cc:6112) > FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6112) > FAIL: g++.dg/modules/xtreme-header-5_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6112) > ... and 10 more entries > > progressions.sum: > === g++ tests === > > Running g++:g++.dg/modules/modules.exp ... > FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6110) > FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2a (internal compiler error: in core_vals, at cp/module.cc:6110) > FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6110) > FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6110) > FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2a (internal compiler error: in core_vals, at cp/module.cc:6110) > FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6110) > FAIL: g++.dg/modules/xtreme-header-5_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6110) > ... and 10 more entries > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/8… . > The full lists of regressions and progressions are in > - https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/8… . > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/8… . > > 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/8… > Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/8… > > 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/f9fbf93dc82525a0f54a2293b7ec92d657… > > List of configurations that regressed due to this commit : > * tcwg_gnu_native_check_gcc > ** master-aarch64 > *** FAIL: 15 regressions: 15 progressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/8…

1 year, 11 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc patch #83947: FAIL: 2 regressions on arm

by chenxiaolong

At 08:36 +0000 on Friday, 2024-01-12, wrote ci_notify(a)linaro.org: > 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. Ok, I will fix this error as soon as possible!

1 year, 11 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-14-6840-g86f535cb466: FAIL: 2 regressions: 2 progressions on arm

by Christophe Lyon

Hi David, As you have probably guessed, this is a false alarm: the testcases you updated were already failing before your patch, but it changed the line numbers, thus making the scripts think a failure disappeared and a new one appeared. Thanks, Christophe On Mon, 8 Jan 2024 at 01: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. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1094 , please let us know if you are looking at the problem and/or when you have a fix. > > In bootstrap_check master-arm-check_bootstrap_lto after: > > | commit gcc-14-6840-g86f535cb466 > | Author: David Edelsohn <dje.gcc(a)gmail.com> > | Date: Tue Dec 26 16:44:09 2023 +0000 > | > | testsuite: Skip analyzer out-of-bounds-diagram on AIX. > | > | The out-of-bounds diagram tests fail on AIX. > | > | gcc/testsuite/ChangeLog: > | * gcc.dg/analyzer/out-of-bounds-diagram-17.c: Skip on AIX. > | * gcc.dg/analyzer/out-of-bounds-diagram-18.c: Same. > | ... 2 lines of the commit log omitted. > > FAIL: 2 regressions: 2 progressions > > regressions.sum: > === gcc tests === > > Running gcc:gcc.dg/analyzer/analyzer.exp ... > FAIL: gcc.dg/analyzer/out-of-bounds-diagram-17.c expected multiline pattern lines 15-36 > FAIL: gcc.dg/analyzer/out-of-bounds-diagram-18.c expected multiline pattern lines 15-44 > > === Results Summary === > > progressions.sum: > === gcc tests === > > Running gcc:gcc.dg/analyzer/analyzer.exp ... > FAIL: gcc.dg/analyzer/out-of-bounds-diagram-17.c expected multiline pattern lines 14-35 > FAIL: gcc.dg/analyzer/out-of-bounds-diagram-18.c expected multiline pattern lines 14-43 > > === Results Summary === > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_bootstrap_check--master-arm-check_bootstrap_… . > The full lists of regressions and progressions are in > - https://ci.linaro.org/job/tcwg_bootstrap_check--master-arm-check_bootstrap_… . > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_bootstrap_check--master-arm-check_bootstrap_… . > > The configuration of this build is: > CI config tcwg_bootstrap_check master-arm-check_bootstrap_lto > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_bootstrap_check--master-arm-check_bootstrap_… > Reference build : https://ci.linaro.org/job/tcwg_bootstrap_check--master-arm-check_bootstrap_… > > 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/86f535cb4664fcaf96ff12942887db949b… > > List of configurations that regressed due to this commit : > * tcwg_bootstrap_check > ** master-arm-check_bootstrap_lto > *** FAIL: 2 regressions: 2 progressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_bootstrap_check--master-arm-check_bootstrap_…

1 year, 11 months

2
1
0 0

[ACTIVITY] report week ending 5 Jan

by Peter Maydell

Progress (short week, 2 days): * UM-2 [QEMU upstream maintainership] - post holiday email/slack/etc catchup - started merging pullrequests (I'm doing release management for the 9.0 cycle) - investigated a reported regression in virtio-pci running Linux on 32-bit arm emulation. This turns out to be that we made a change that *fixed* a bug in QEMU (we were incorrectly laying out the 'virt' board assuming a 32-bit v8 CPU couldn't use LPAE), which reveals a bug in Linux (it mishandles the PCI controller DTB entry saying the ECAM region is above the 4GB boundary)... * QEMU-623 [Nested Virtualization Emulation] - dealt with the minor review followups on this patchset; just waiting for one last reviewed-by tag before we can upstream it -- PMM

1 year, 11 months

1
0
0 0

RE: [Linaro-TCWG-CI] gcc-14-6861-g200531d5b9f: FAIL: 1 regressions on arm

by Andrew Pinski (QUIC)

> -----Original Message----- > From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> > Sent: Friday, December 29, 2023 7:40 AM > To: Andrew Pinski (QUIC) <quic_apinski(a)quicinc.com> > Cc: gcc-regression(a)gcc.gnu.org > Subject: [Linaro-TCWG-CI] gcc-14-6861-g200531d5b9f: FAIL: 1 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. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1091 , > please let us know if you are looking at the problem and/or when you have a > fix. First I suspect this was failing before r14-6822-g01f4251b8775c8 and I just return it back to that state. The big ask I have is for reports like this, to include the exact gcc configure line that was used. In this case, is GCC configured to include neon by default? If so then the testcase needs to be updated to add an option to disable neon. If not, then someone else will need to look into why the testcase is failing. Basically, the update I did was disable vectorization on a loop which was not being vectorized before r14-6822-g01f4251b8775c8. Thanks, Andrew Pinski > > In master-arm after: > > | commit gcc-14-6861-g200531d5b9f > | Author: Andrew Pinski <quic_apinski(a)quicinc.com> > | Date: Thu Dec 28 20:26:01 2023 -0800 > | > | Fix gen-vect-26.c testcase after loops with multiple exits [PR113167] > | > | This fixes the gcc.dg/tree-ssa/gen-vect-26.c testcase by adding > | `#pragma GCC novector` in front of the loop that is doing the checking > | of the result. We only want to test the first loop to see if it can be > | vectorize. > | > | ... 9 lines of the commit log omitted. > > FAIL: 1 regressions > > regressions.sum: > === gcc tests === > > Running gcc:gcc.dg/tree-ssa/tree-ssa.exp ... > FAIL: gcc.dg/tree-ssa/gen-vect-26.c scan-tree-dump-times vect "Alignment of > access forced using peeling" 1 > > === Results Summary === > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm- > build/1147/artifact/artifacts/00-sumfiles/ . > The full lists of regressions and progressions are in > - https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm- > build/1147/artifact/artifacts/notify/ . > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm- > build/1147/artifact/artifacts/sumfiles/xfails.xfail . > > The configuration of this build is: > CI config tcwg_gnu_cross_check_gcc master-arm > > -----------------8<--------------------------8<--------------------------8<---------------- > ---------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master- > arm-build/1147/artifact/artifacts > Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc-- > master-arm-build/1146/artifact/artifacts > > Reproduce last good and first bad builds: https://git- > us.linaro.org/toolchain/ci/interesting- > commits.git/plain/gcc/sha1/200531d5b9fb99eca2b0d6b8d1e42d17641322 > 5f/tcwg_gnu_cross_check_gcc/master-arm/reproduction_instructions.txt > > Full commit : https://github.com/gcc- > mirror/gcc/commit/200531d5b9fb99eca2b0d6b8d1e42d176413225f > > List of configurations that regressed due to this commit : > * tcwg_gnu_cross_check_gcc > ** master-arm > *** FAIL: 1 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting- > commits.git/plain/gcc/sha1/200531d5b9fb99eca2b0d6b8d1e42d17641322 > 5f/tcwg_gnu_cross_check_gcc/master-arm/details.txt > *** https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm- > build/1147/artifact/artifacts

1 year, 11 months

2
1
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain