linaro-toolchain January 2024

linaro-toolchain@lists.linaro.org

16 participants
25 discussions

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…

9 months, 3 weeks

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.

9 months, 3 weeks

[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…

9 months, 3 weeks

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.

10 months

[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

10 months

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.

10 months

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

10 months

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…

10 months

[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

10 months, 1 week

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…

10 months, 1 week

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain January 2024