- linaro-toolchain - lists.linaro.org

by Peter Maydell

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

1 year

1
0
0 0

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

by Andrew Pinski (QUIC)

These are all expected "failures" for arm (aarch32) really; the new testcases were known to fail for that target; it is recorded as PR 224847. I was not sure how to record this besides in the commit message. Should I xfail them for the targets that are known to fail? Thanks, Andrew Pinski > -----Original Message----- > From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> > Sent: Friday, April 26, 2024 3:15 PM > To: Andrew Pinski (QUIC) <quic_apinski(a)quicinc.com> > Subject: [Linaro-TCWG-CI] gcc patch #89057: FAIL: 28 regressions on arm > > Dear contributor, our automatic CI has detected problems related to your > patch(es). Please find some details below. If you have any questions, please > follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg > channel, or ping your favourite Linaro toolchain developer on the usual project > channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce > the issue locally. If you can't get what you need from our CI within minutes, let > us know and we will be happy to help. > > In gcc_check master-arm after: > > | gcc patch https://patchwork.sourceware.org/patch/89057 > | Author: Andrew Pinski <quic_apinski(a)quicinc.com> > | Date: Fri Apr 26 10:07:40 2024 -0700 > | > | aarch64: Fix normal returns inside functions which use eh_returns > [PR114843] > | > | The problem here is that on a normal return path, we still restore the > | eh data return when we should not. > | Instead of one return path in the case of eh_return, this changes over > | to use multiple returns pathes just like a normal function. > | On the normal path (non-eh return), we need to skip restoring of the eh > | ... 43 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 6b86f71165d AArch64: Cleanup memset expansion > > FAIL: 28 regressions > > regressions.sum: > === gcc tests === > > Running gcc:gcc.c-torture/execute/execute.exp ... > FAIL: gcc.c-torture/execute/eh_return-1.c -O0 execution test > FAIL: gcc.c-torture/execute/eh_return-1.c -O1 execution test > FAIL: gcc.c-torture/execute/eh_return-1.c -O2 execution test > FAIL: gcc.c-torture/execute/eh_return-1.c -O2 -flto -fno-use-linker-plugin - > flto-partition=none execution test > FAIL: gcc.c-torture/execute/eh_return-1.c -O2 -flto -fuse-linker-plugin -fno- > fat-lto-objects execution test > FAIL: gcc.c-torture/execute/eh_return-1.c -O3 -g execution test > FAIL: gcc.c-torture/execute/eh_return-1.c -Os execution test ... and 22 more > entries > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm- > precommit/6993/artifact/artifacts/artifacts.precommit/00-sumfiles/ > The full lists of regressions and progressions as well as configure and make > commands are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm- > precommit/6993/artifact/artifacts/artifacts.precommit/notify/ > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm- > precommit/6993/artifact/artifacts/artifacts.precommit/sumfiles/xfails.xfail > > The configuration of this build is: > CI config tcwg_gcc_check master-arm > > -----------------8<--------------------------8<--------------------------8<---------------- > ---------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm- > precommit/6993/artifact/artifacts > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm- > build/2027/artifact/artifacts > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the master > files.

1 year

2
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

1
0
0 0

gcc patch #88922: FAIL: 1 regressions on aarch64

by Paul Richard Thomas

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

1 year

2
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

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

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

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

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

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, 1 month

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, 1 month

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, 1 month

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, 1 month

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, 1 month

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, 1 month

1
0
0 0

Re: [Linaro-TCWG-CI] gcc patch #88035: FAIL: 1 regressions on aarch64

by Jonathan Wakely

On Thu, 4 Apr 2024 at 22:21, <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. Hi, The new testcase only works for targets where char is signed, because I forgot to add the assertions for the unsigned case. My own aarch64 testing found the same problem. I'll send a v2 patch shortly. Thanks for the useful CI service! > > 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/88035 > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Thu Apr 4 16:29:09 2024 +0100 > | > | libstdc++: Fix infinite loop in std::istream::ignore(n, delim) [PR93672] > | > | I would appreciate more eyes on this to confirm my conclusions about > | negative int_type values, and the proposed fix, make sense. > | > | Tested x86_64-linux. > | > | ... 32 lines of the commit log omitted. > | ... applied on top of baseline commit: > | dc8a25189dd Add gcov MC/DC tests for GDC > > FAIL: 1 regressions > > regressions.sum: > === libstdc++ tests === > > Running libstdc++:libstdc++-dg/conformance.exp ... > FAIL: 27_io/basic_istream/ignore/char/93672.cc -std=gnu++17 execution test > > > # of stable fails 61 > # of flaky entries 9 > # of all tests 890731 > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/5627/art… > 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-precommit/5627/art… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/5627/art… > > 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-precommit/5627/art… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1805/artifac… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files.

1 year, 1 month

1
0
0 0

[Linaro-TCWG-CI] binutils-2_41-release-2766-ga9505c74206: 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-1188 , 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-2766-ga9505c74206 | Author: H.J. Lu <hjl.tools(a)gmail.com> | Date: Mon Mar 11 09:51:06 2024 -0700 | | elf: Add _bfd_elf_link_m[un]map_section_contents | | To copy input section contents, add _bfd_elf_link_mmap_section_contents | and _bfd_elf_link_munmap_section_contents to mmap in the input sections. | | * elf-bfd.h (_bfd_elf_link_mmap_section_contents): New. | (_bfd_elf_link_munmap_section_contents): Likewise. | ... 13 lines of the commit log omitted. FAIL: 1 regressions regressions.sum: === glibc tests === Running glibc:wcsmbs ... FAIL: wcsmbs/tst-wcstod-round # of stable fails 1 # of flaky entries 16 # of all tests 4848 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=a9505c74206cf… List of configurations that regressed due to this commit : * tcwg_gnu_native_check_glibc ** master-aarch64 *** FAIL: 1 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti… *** https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-aarch64-build…

1 year, 1 month

3
2
0 0

[Linaro-TCWG-CI] glibc-2.39.9000-128-ga4ed0471d7: FAIL: 4 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-1187 , please let us know if you are looking at the problem and/or when you have a fix. In master-aarch64 after: | commit glibc-2.39.9000-128-ga4ed0471d7 | Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> | Date: Thu Jan 18 10:18:01 2024 -0300 | | Always define __USE_TIME_BITS64 when 64 bit time_t is used | | It was raised on libc-help [1] that some Linux kernel interfaces expect | the libc to define __USE_TIME_BITS64 to indicate the time_t size for the | kABI. Different than defined by the initial y2038 design document [2], | the __USE_TIME_BITS64 is only defined for ABIs that support more than | one time_t size (by defining the _TIME_BITS for each module). | ... 12 lines of the commit log omitted. FAIL: 4 regressions regressions.sum: === g++ tests === Running g++:g++.dg/tsan/tsan.exp ... FAIL: g++.dg/tsan/pthread_cond_clockwait.C -O0 (test for excess errors) UNRESOLVED: g++.dg/tsan/pthread_cond_clockwait.C -O0 compilation failed to produce executable FAIL: g++.dg/tsan/pthread_cond_clockwait.C -O2 (test for excess errors) UNRESOLVED: g++.dg/tsan/pthread_cond_clockwait.C -O2 compilation failed to produce executable ... and 2 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/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/glibc/… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=a4ed0471d71739928a0d… List of configurations that regressed due to this commit : * tcwg_gnu_native_check_gcc ** master-aarch64 *** FAIL: 4 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… *** https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/1…

1 year, 1 month

1
0
0 0

clang-aarch64-sve-vls-2stage workers

by Vitaly Buka

Looks like one worker in a bad state? https://lab.llvm.org/buildbot/#/builders/176 https://lab.llvm.org/buildbot/#/workers/207 is green https://lab.llvm.org/buildbot/#/workers/209 is red Would it be possible to fix or shut down a bad worker? Thank you!

1 year, 1 month

2
2
0 0

Re: [Linaro-TCWG-CI] gdb patch #87686: FAIL: 7 regressions: 16 progressions on arm

by Maxim Kuvyrkov

Hi Christina, This is false-positive report -- see https://sourceware.org/bugzilla/show_bug.cgi?id=31575 for details. -- Maxim Kuvyrkov https://www.linaro.org > On Mar 29, 2024, at 10:22, 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-arm after: > > | gdb patch https://patchwork.sourceware.org/patch/87686 > | Author: Christina Schimpe <christina.schimpe(a)intel.com> > | Date: Wed Mar 27 07:47:37 2024 +0000 > | > | gdb: Make tagged pointer support configurable. > | > | The gdbarch function gdbarch_remove_non_address_bits adjusts addresses to > | enable debugging of programs with tagged pointers on Linux, for instance for > | ARM's feature top byte ignore (TBI). > | Once the function is implemented for an architecture, it adjusts addresses for > | memory access, breakpoints and watchpoints. > | ... 12 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 1678a15b694 Automatic date update in version.in > > FAIL: 7 regressions: 16 progressions > > regressions.sum: > === gdb tests === > > Running gdb:gdb.ada/verylong.exp ... > FAIL: gdb.ada/verylong.exp: print (x / 4) * 2 > FAIL: gdb.ada/verylong.exp: print +x > FAIL: gdb.ada/verylong.exp: print -x > FAIL: gdb.ada/verylong.exp: print x > FAIL: gdb.ada/verylong.exp: print x - 99 + 1 > FAIL: gdb.ada/verylong.exp: print x / 2 > FAIL: gdb.ada/verylong.exp: print x = 170141183460469231731687303715884105727 > ... and 1 more entries > > progressions.sum: > === gdb tests === > > Running gdb:gdb.ada/convvar_comp.exp ... > FAIL: gdb.ada/convvar_comp.exp: print $item.started > FAIL: gdb.ada/convvar_comp.exp: print item.started > FAIL: gdb.ada/convvar_comp.exp: set variable $item := item > > Running gdb:gdb.ada/enum_idx_packed.exp ... > FAIL: gdb.ada/enum_idx_packed.exp: scenario=minimal: print small > FAIL: gdb.ada/enum_idx_packed.exp: scenario=minimal: print multi_multi(1,3) > ... and 18 more entries > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/2024/artifac… > 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/2024/artifac… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/2024/artifac… > > 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/2024/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/984/artifact/art… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files.

1 year, 1 month

1
0
0 0

Re: [Linaro-TCWG-CI] gdb patch #87793: FAIL: 7 regressions: 16 progressions on arm

by Maxim Kuvyrkov

Hi Kevin, This is false-positive report -- see https://sourceware.org/bugzilla/show_bug.cgi?id=31575 for details. -- Maxim Kuvyrkov https://www.linaro.org > On Mar 29, 2024, at 10:48, 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-arm after: > > | gdb patch https://patchwork.sourceware.org/patch/87793 > | Author: Kevin Buettner <kevinb(a)redhat.com> > | Date: Thu Mar 28 15:53:14 2024 -0700 > | > | New test: gdb.base/check-errno.exp > | > | Printing the value of 'errno' from GDB is sometimes problematic. The > | situation has improved in recent years, though there are still > | scenarios for which "print errno" doesn't work. > | > | The test, gdb.base/check-errno.exp, introduced by this commit, > | ... 174 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 1678a15b694 Automatic date update in version.in > > FAIL: 7 regressions: 16 progressions > > regressions.sum: > === gdb tests === > > Running gdb:gdb.ada/verylong.exp ... > FAIL: gdb.ada/verylong.exp: print (x / 4) * 2 > FAIL: gdb.ada/verylong.exp: print +x > FAIL: gdb.ada/verylong.exp: print -x > FAIL: gdb.ada/verylong.exp: print x > FAIL: gdb.ada/verylong.exp: print x - 99 + 1 > FAIL: gdb.ada/verylong.exp: print x / 2 > FAIL: gdb.ada/verylong.exp: print x = 170141183460469231731687303715884105727 > ... and 1 more entries > > progressions.sum: > === gdb tests === > > Running gdb:gdb.ada/convvar_comp.exp ... > FAIL: gdb.ada/convvar_comp.exp: print item.started > FAIL: gdb.ada/convvar_comp.exp: set variable $item := item > FAIL: gdb.ada/convvar_comp.exp: print $item.started > > Running gdb:gdb.ada/enum_idx_packed.exp ... > FAIL: gdb.ada/enum_idx_packed.exp: scenario=minimal: print small > FAIL: gdb.ada/enum_idx_packed.exp: scenario=minimal: print multi > ... and 18 more entries > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/2028/artifac… > 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/2028/artifac… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/2028/artifac… > > 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/2028/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/984/artifact/art… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files.

1 year, 1 month

1
0
0 0

Re: [Linaro-TCWG-CI] 8 patches in gdb: FAIL: 7 regressions: 16 progressions on arm

by Maxim Kuvyrkov

Hi Abdul, Hi Nils, This is false-positive report -- see https://sourceware.org/bugzilla/show_bug.cgi?id=31575 for details. -- Maxim Kuvyrkov https://www.linaro.org > On Mar 29, 2024, at 10:52, 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-arm after: > > | 8 patches in gdb > | Patchwork URL: https://patchwork.sourceware.org/patch/87768 > | 96ab853e5d4 gdb, mi: Skip trampoline functions for the -stack-list-frames command. > | e2c217f4226 gdb: Skip trampoline functions for the return command. > | 687b0373e1e gdb: Skip trampoline functions for the up command. > | 5f8cc05162b gdb: Skip trampoline functions for the finish and reverse-finish commands. > | 287546c56c8 gdb: Skip trampoline frames for the backtrace command. > | ... and 3 more patches in gdb > | ... applied on top of baseline commit: > | 1678a15b694 Automatic date update in version.in > > FAIL: 7 regressions: 16 progressions > > regressions.sum: > === gdb tests === > > Running gdb:gdb.ada/verylong.exp ... > FAIL: gdb.ada/verylong.exp: print (x / 4) * 2 > FAIL: gdb.ada/verylong.exp: print +x > FAIL: gdb.ada/verylong.exp: print -x > FAIL: gdb.ada/verylong.exp: print x > FAIL: gdb.ada/verylong.exp: print x - 99 + 1 > FAIL: gdb.ada/verylong.exp: print x / 2 > FAIL: gdb.ada/verylong.exp: print x = 170141183460469231731687303715884105727 > ... and 1 more entries > > progressions.sum: > === gdb tests === > > Running gdb:gdb.ada/convvar_comp.exp ... > FAIL: gdb.ada/convvar_comp.exp: set variable $item := item > FAIL: gdb.ada/convvar_comp.exp: print $item.started > FAIL: gdb.ada/convvar_comp.exp: print item.started > > Running gdb:gdb.ada/enum_idx_packed.exp ... > FAIL: gdb.ada/enum_idx_packed.exp: scenario=minimal: ptype multi > FAIL: gdb.ada/enum_idx_packed.exp: scenario=minimal: ptype small > ... and 18 more entries > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/2026/artifac… > 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/2026/artifac… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/2026/artifac… > > 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/2026/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/984/artifact/art… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files.

1 year, 1 month

1
0
0 0

Re: [Linaro-TCWG-CI] 4 patches in gdb: FAIL: 7 regressions: 16 progressions on arm

by Maxim Kuvyrkov

Hi Gustavo, This is false-positive report -- see https://sourceware.org/bugzilla/show_bug.cgi?id=31575 for details. -- Maxim Kuvyrkov https://www.linaro.org > On Mar 29, 2024, at 10:54, 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-arm after: > > | 4 patches in gdb > | Patchwork URL: https://patchwork.sourceware.org/patch/87792 > | 81f55c5f65e gdb: Add new remote packet to check if address is tagged > | c72332af687 gdb: aarch64: Remove MTE address checking from memtag_matches_p > | d1ba7d95516 gdb: aarch64: Move MTE address check out of set_memtag > | 9769943c7d4 gdb: aarch64: Remove MTE address checking from get_memtag > | ... applied on top of baseline commit: > | 1678a15b694 Automatic date update in version.in > > FAIL: 7 regressions: 16 progressions > > regressions.sum: > === gdb tests === > > Running gdb:gdb.ada/verylong.exp ... > FAIL: gdb.ada/verylong.exp: print (x / 4) * 2 > FAIL: gdb.ada/verylong.exp: print +x > FAIL: gdb.ada/verylong.exp: print -x > FAIL: gdb.ada/verylong.exp: print x > FAIL: gdb.ada/verylong.exp: print x - 99 + 1 > FAIL: gdb.ada/verylong.exp: print x / 2 > FAIL: gdb.ada/verylong.exp: print x = 170141183460469231731687303715884105727 > ... and 1 more entries > > progressions.sum: > === gdb tests === > > Running gdb:gdb.ada/convvar_comp.exp ... > FAIL: gdb.ada/convvar_comp.exp: print item.started > FAIL: gdb.ada/convvar_comp.exp: print $item.started > FAIL: gdb.ada/convvar_comp.exp: set variable $item := item > > Running gdb:gdb.ada/enum_idx_packed.exp ... > FAIL: gdb.ada/enum_idx_packed.exp: scenario=minimal: ptype small > FAIL: gdb.ada/enum_idx_packed.exp: scenario=minimal: print multi_multi(2) > ... and 18 more entries > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/2027/artifac… > 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/2027/artifac… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/2027/artifac… > > 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/2027/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/984/artifact/art… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files.

1 year, 1 month

1
0
0 0

[ACTIVITY] report week ending 28 Mar

by Peter Maydell

Progress (short week, 3 days): * UM-2 [QEMU upstream maintainership] - more FEAT_NMI patchset review: done with the physical interrupt parts, haven't looked at the virtual interrupt parts yet - usual release related effort - investigated and fixed a bug where we were taking HSTR traps to the wrong EL - noticed a minor GIC bug where HPPIR reads weren't honouring the interrupt-group-disable bits; sent a patch - reviewed the latest STM32L4x5 UART patchset -- PMM

1 year, 1 month

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-14-9157-gff442719cdb: slowed down by 23% - 549.fotonik3d_r on aarch64 O3

by Maxim Kuvyrkov

Hi Richard, Heads up, our benchmarking CI flagged your commit to cause 23% regression in 549.fotonik3d_r on Cortex-A57 at -O3. Do you have internal benchmarks for this change? Thanks! -- Maxim Kuvyrkov https://www.linaro.org > On Mar 24, 2024, at 03:43, 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-1181 , please let us know if you are looking at the problem and/or when you have a fix. > > In CI config tcwg_bmk-code_speed-cpu2017rate/gnu-aarch64-master-O3 after: > > | commit gcc-14-9157-gff442719cdb > | Author: Richard Sandiford <richard.sandiford(a)arm.com> > | Date: Fri Feb 23 14:12:55 2024 +0000 > | > | aarch64: Spread out FPR usage between RA regions [PR113613] > | > | early-ra already had code to do regrename-style "broadening" > | of the allocation, to promote scheduling freedom. However, > | the pass divides the function into allocation regions > | and this broadening only worked within a single region. > | This meant that if a basic block contained one subblock > | ... 30 lines of the commit log omitted. > > the following benchmarks slowed down by more than 3%: > - slowed down by 23% - 549.fotonik3d_r - from 16467 to 20213 perf samples > the following hot functions slowed down by more than 15% (but their benchmarks slowed down by less than 3%): > - slowed down by 88% - 549.fotonik3d_r:[.] __material_mod_MOD_mat_updatee - from 4373 to 8204 perf samples > > The configuration of this build is: > Below reproducer instructions can be used to re-build both "first_bad" and "last_good" cross-toolchains used in this bisection. Naturally, the scripts will fail when triggerring benchmarking jobs if you don\'t have access to Linaro TCWG CI. > > Configuration: > - Benchmark: SPEC CPU2017 > - Toolchain: GCC + Glibc + GNU Linker > - Version: all components were built from their tip of trunk > - Target: aarch64-linux-gnu > - Compiler flags: O3 > - Hardware: NVidia TX1 4x Cortex-A57 > > This benchmarking CI is work-in-progress, and we welcome feedback and suggestions at linaro-toolchain(a)lists.linaro.org . In our improvement plans is to add support for SPEC CPU2017 benchmarks and provide "perf report/annotate" data behind these reports. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_bmk-code_speed-cpu2017rate--gnu-aarch64-mast… > Reference build : https://ci.linaro.org/job/tcwg_bmk-code_speed-cpu2017rate--gnu-aarch64-mast… > > 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/ff442719cdb64c9df9d069af88e90d51be… > > List of configurations that regressed due to this commit : > * tcwg_bmk-code_speed-cpu2017rate > ** gnu-aarch64-master-O3 > *** slowed down by 23% - 549.fotonik3d_r > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_bmk-code_speed-cpu2017rate--gnu-aarch64-mast…

1 year, 1 month

2
1
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain