- 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

[ACTIVITY] report week ending 22 Mar

by Peter Maydell

Progress (short week, 3 days): * UM-2 [QEMU upstream maintainership] - more softfreeze related work: tagged rc0 this week - spent some time looking through Huawei's FEAT_NMI patchset; this is in basically good shape but there are a number of minor bugs/missing bits of the feature for them to work through still - reviewed a patchset adding nucleo-g071rb (an STM32G0 based board) -- PMM

1 year, 1 month

1
0
0 0

LLVM buildbot clang-aarch64-full-2stage

by orlando.hyams＠sony.com

Hi, I noticed this address registered as the admin for this LLVM buildbot - https://lab.llvm.org/buildbot/#/workers/134). I caused a failure at the start of the week (https://lab.llvm.org/buildbot/#/builders/179/builds/9629). I think it's a build (or test) configuration problem as outlined in this small PR https://github.com/llvm/llvm-zorg/pull/139. I can see the bot is currently failing now too (https://lab.llvm.org/buildbot/#/builders/179/builds/9681). I haven't looked at it closely but given the same tests are failing in a similar way (a different bitcode error from LLD), I imagine that might also be fixed by my llvm-zorg pull request above? Please can someone look at the llvm-zorg pull request when you have a spare moment? I have my LLVM change that caused the initial failure reverted in the meantime. Thanks, Orlando

1 year, 1 month

2
2
0 0

Re: [Linaro-TCWG-CI] gcc-14-9478-gdf483ebd246: FAIL: 7 regressions on aarch64

by Jonathan Wakely

Oops. Jakub has fixed this now. On Thu, 14 Mar 2024 at 23:45, <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-1177 , 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-9478-gdf483ebd246 > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Mon Feb 26 13:17:13 2024 +0000 > | > | libstdc++: Add nodiscard in <algorithm> > | > | Add the [[nodiscard]] attribute to several functions in <algorithm>. > | These all have no side effects and are only called for their return > | value (e.g. std::count) or produce a result that must not be discarded > | for correctness (e.g. std::remove). > | > | ... 49 lines of the commit log omitted. > > FAIL: 7 regressions > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/torture/dg-torture.exp ... > FAIL: g++.dg/torture/pr104601.C -O0 (test for excess errors) > FAIL: g++.dg/torture/pr104601.C -O1 (test for excess errors) > FAIL: g++.dg/torture/pr104601.C -O2 (test for excess errors) > FAIL: g++.dg/torture/pr104601.C -O2 -flto -fno-use-linker-plugin -flto-partition=none (test for excess errors) > FAIL: g++.dg/torture/pr104601.C -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects (test for excess errors) > FAIL: g++.dg/torture/pr104601.C -O3 -g (test for excess errors) > FAIL: g++.dg/torture/pr104601.C -Os (test for excess errors) > ... and 1 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/1715/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/1715/artifac… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1715/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/1715/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1714/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/df483ebd24689a3bebfae2089637a00eca… > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-aarch64 > *** FAIL: 7 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/1715/artifac…

1 year, 2 months

1
0
0 0

[ACTIVITY] report week ending 14 Mar

by Peter Maydell

Progress (short week, 3 days): * UM-2 [QEMU upstream maintainership] - softfreeze week this week, so a lot of time shepherding patches and pullrequests upstream, looking to see if we have any bugs that we ought to fix for 9.0, etc - looked at our Coverity results and submitted patches for seven random easy-to-fix issues -- PMM

1 year, 2 months

1
0
0 0

[Linaro-TCWG-CI] glibc-2.39.9000-100-g2367bf468c: 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-1176 , 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.39.9000-100-g2367bf468c | Author: Joseph Myers <josmyers(a)redhat.com> | Date: Wed Mar 13 19:46:21 2024 +0000 | | Update kernel version to 6.8 in header constant tests | | This patch updates the kernel version in the tests tst-mman-consts.py, | tst-mount-consts.py and tst-pidfd-consts.py to 6.8. (There are no new | constants covered by these tests in 6.8 that need any other header | changes.) | | ... 1 lines of the commit log omitted. FAIL: 1 regressions regressions.sum: === glibc tests === Running glibc:misc ... FAIL: misc/tst-pidfd-consts 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/623… 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-arm-build/623… The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/623… 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/623… Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/622… 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=2367bf468ce43801de98… 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/623…

1 year, 2 months

1
0
0 0

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

by Maxim Kuvyrkov

> On Jan 30, 2024, at 23:03, 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-1136 , please let us know if you are looking at the problem and/or when you have a fix. > > In master-arm after: > > | commit gdb-14-branchpoint-1411-g033bc67bdb0 > | Author: Tom Tromey <tom(a)tromey.com> > | Date: Tue Sep 19 17:39:31 2023 -0600 > | > | Only search types in cp_lookup_rtti_type > | > | This changes cp_lookup_rtti_type to only search for types -- not > | functions or variables. Due to the symbol-matching hack, this could > | just use SEARCH_TYPE_DOMAIN, but I think it's better to be clear; also > | I hold on to some hope that perhaps the hack can someday be removed. > > FAIL: 2 regressions > > regressions.sum: > === libstdc++ tests === > > Running libstdc++:libstdc++-prettyprinters/prettyprinters.exp ... > FAIL: libstdc++-prettyprinters/cxx11.cc print ecmiaow > FAIL: libstdc++-prettyprinters/cxx11.cc print emiaow Hi Tom, Hi Jonathan, After the above GDB patch I see 2 new failures both for aarch64-linux-gnu and arm-linux-gnueabihf in GCC's libstdc++ testsuite. The log [1] says: === $35 = warning: RTTI symbol not found for class 'main::custom_cat' warning: RTTI symbol not found for class 'main::custom_cat' got: $35 = warning: RTTI symbol not found for class 'main::custom_cat' FAIL: libstdc++-prettyprinters/cxx11.cc print emiaow skipping: warning: RTTI symbol not found for class 'main::custom_cat' std::error_code = {std::_V2::error_category: 42} skipping: std::error_code = {std::_V2::error_category: 42} $36 = warning: RTTI symbol not found for class 'main::custom_cat' warning: RTTI symbol not found for class 'main::custom_cat' got: $36 = warning: RTTI symbol not found for class 'main::custom_cat' FAIL: libstdc++-prettyprinters/cxx11.cc print ecmiaow === Which way should I dig -- GDB or libstdc++? Does this look like libstdc++ testcase needs an update? [1] https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/l… Thanks! -- Maxim Kuvyrkov https://www.linaro.org > > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/987/a… > 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-arm-build/987/a… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/987/a… > > The configuration of this build is: > CI config tcwg_gnu_native_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_native_check_gcc--master-arm-build/987/a… > Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/986/a… > > 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=033bc67bdb0c7… > > List of configurations that regressed due to this commit : > * tcwg_gnu_native_check_gcc > ** master-arm > *** FAIL: 2 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-arm-build/987/a…

1 year, 2 months

3
4
0 0

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

by Maxim Kuvyrkov

> On Jan 27, 2024, at 17:25, 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-1121 , please let us know if you are looking at the problem and/or when you have a fix. > > In master-arm after: > > | commit gdb-14-branchpoint-1356-g7737b133640 > | Author: Tom Tromey <tromey(a)adacore.com> > | Date: Tue Jan 9 11:47:17 2024 -0700 > | > | Handle DW_AT_endianity on enumeration types > | > | A user found that gdb would not correctly print a field from an Ada > | record using the scalar storage order feature. We tracked this down > | to a combination of problems. > | > | First, GCC did not emit DW_AT_endianity on the enumeration type. > | ... 14 lines of the commit log omitted. > > FAIL: 1 regressions > > regressions.sum: > === gdb tests === > > Running gdb:gdb.ada/scalar_storage.exp ... > FAIL: gdb.ada/scalar_storage.exp: print V_BE Hi Tom, I see the above failure for both aarch64-linux-gnu and arm-linux-gnueabihf in our testing. The log shows ([1]): === Breakpoint 1, storage () at /home/tcwg-buildslave/workspace/tcwg_gnu_2/gdb/gdb/testsuite/gdb.ada/scalar_storage/storage.adb:53 53 Do_Nothing (V_LE'Address); -- START (gdb) print V_LE $1 = (value => 126, another_value => 12, color => green) (gdb) PASS: gdb.ada/scalar_storage.exp: print V_LE get_compiler_info: gcc-14-0-1 print V_BE $2 = (value => 126, another_value => 12, color => red) (gdb) FAIL: gdb.ada/scalar_storage.exp: print V_BE === Any idea what can be causing this? This failure happens in CI configurations where we track tip-of-trunk GCC. [1] https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/l… 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_gnu_native_check_gdb--master-arm-build/1076/… . > The full lists of regressions and progressions are in > - https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1076/… . > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1076/… . > > The configuration of this build is: > CI config tcwg_gnu_native_check_gdb 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_gdb--master-arm-build/1076/… > Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1075/… > > 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=7737b1336402c… > > List of configurations that regressed due to this commit : > * tcwg_gnu_native_check_gdb > ** master-arm > *** FAIL: 1 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sh… > *** https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1076/…

1 year, 2 months

2
2
0 0

Re: [Linaro-TCWG-CI] gcc-14-8680-g2f14c0dbb78: FAIL: 3 regressions on arm

by Maxim Kuvyrkov

> On Feb 1, 2024, at 16:07, ci_notify--- via Gcc-regression <gcc-regression(a)gcc.gnu.org> wrote: > > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1140 , please let us know if you are looking at the problem and/or when you have a fix. > > In gcc_check master-arm after: > > | commit gcc-14-8680-g2f14c0dbb78 > | Author: Roger Sayle <roger(a)nextmovesoftware.com> > | Date: Thu Feb 1 06:10:42 2024 +0000 > | > | PR target/113560: Enhance is_widening_mult_rhs_p. > | > | This patch resolves PR113560, a code quality regression from GCC12 > | affecting x86_64, by enhancing the middle-end's tree-ssa-math-opts.cc > | to recognize more instances of widening multiplications. > | > | The widening multiplication perception code identifies cases like: > | ... 116 lines of the commit log omitted. > > FAIL: 3 regressions > > regressions.sum: > === gcc tests === > > Running gcc:gcc.target/arm/arm.exp ... > FAIL: gcc.target/arm/wmul-5.c scan-assembler umlal > FAIL: gcc.target/arm/wmul-6.c scan-assembler smlalbb > FAIL: gcc.target/arm/wmul-7.c scan-assembler umlal Hi Roger, Your patch seems to regress the above 3 tests for all 32-bit ARM targets (see [1]). Would you please check if the regressions can be avoided? For reference, here are configure options we use for arm-linux-gnueabihf cross-toolchain: [2]. [1] https://linaro.atlassian.net/browse/GNU-1140 [2] https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/1303/a… Thanks! -- Maxim Kuvyrkov https://www.linaro.org > > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1650/artifact/ar… > 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-build/1650/artifact/ar… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1650/artifact/ar… > > The configuration of this build is: > CI config tcwg_gcc_check master-arm > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1650/artifact/ar… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1649/artifact/ar… > > Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://github.com/gcc-mirror/gcc/commit/2f14c0dbb789852947cb58fdf7d3162413… > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-arm > *** FAIL: 3 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1650/artifact/ar…

1 year, 2 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-14-8492-g1a8261e047f: FAIL: 3 regressions on arm

by Maxim Kuvyrkov

> On Jan 30, 2024, at 00:35, ci_notify--- via Gcc-regression <gcc-regression(a)gcc.gnu.org> wrote: > > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1132 , please let us know if you are looking at the problem and/or when you have a fix. > > In gcc_check master-arm after: > > | commit gcc-14-8492-g1a8261e047f > | Author: Richard Sandiford <richard.sandiford(a)arm.com> > | Date: Mon Jan 29 12:33:08 2024 +0000 > | > | vect: Tighten vect_determine_precisions_from_range [PR113281] > | > | This was another PR caused by the way that > | vect_determine_precisions_from_range handles shifts. We tried to > | narrow 32768 >> x to a 16-bit shift based on range information for > | the inputs and outputs, with vect_recog_over_widening_pattern > | (after PR110828) adjusting the shift amount. But this doesn't > | ... 36 lines of the commit log omitted. > > FAIL: 3 regressions > > regressions.sum: > === gcc tests === > > Running gcc:gcc.target/arm/simd/simd.exp ... > FAIL: gcc.target/arm/simd/mve-vshr.c scan-assembler-times vneg.s[0-9]+\\tq[0-9]+, q[0-9]+ 6 > FAIL: gcc.target/arm/simd/mve-vshr.c scan-assembler-times vshl.s[0-9]+\\tq[0-9]+, q[0-9]+ 3 > FAIL: gcc.target/arm/simd/mve-vshr.c scan-assembler-times vshl.u[0-9]+\\tq[0-9]+, q[0-9]+ 3 Hi Richard, Could you please check whether the above tests need an update after your patch? We see these tests now consistently failing across all 32-bit ARM configurations that we track (see [1]). As an example, our configure options for arm-linux-gnueabihf that show the failure are at [2]. [1] https://linaro.atlassian.net/browse/GNU-1132 [2] https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/lastSuccessfulBu… 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_gcc_check--master-arm-build/1636/artifact/ar… . > The full lists of regressions and progressions are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1636/artifact/ar… . > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1636/artifact/ar… . > > The configuration of this build is: > CI config tcwg_gcc_check master-arm > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1636/artifact/ar… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1635/artifact/ar… > > Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://github.com/gcc-mirror/gcc/commit/1a8261e047f7a2c2b0afb95716f7615cba… > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-arm > *** FAIL: 3 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1636/artifact/ar…

1 year, 2 months

1
0
0 0

[ACTIVITY] report week ending 8 Mar

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] - code review (softfreeze is next week!): + Add device STM32L4x5 RCC + Add support for I2C in BCM2835 boards + hw/scsi/lsi53c895a: add timer to scripts processing + target/arm: Do memory alignment check for device memory + linux-user: Implement some prctls + some minor patches fixing CI job breakage (FreeBSD 13.2 -> 13.3 change, Python has dropped 'distutils') + a patchset improving the robustness of the elf2dmp utility when fed a corrupt crashfile + get our Coverity Scan submission under gitlab CI control rather than a developer's work machine - summarised discussion about deprecating older Arm board models; sent out patch to mark deprecated all PXA2xx and OMAP2 boards, plus one OMAP1 board that we have no test images for - triaged some new Coverity issues * QEMU-530 [QEMU ARMv9.5 Baseline CPU for TCG] - Sent FEAT_ECV patchset out for code review, addressed minor review comments -- PMM

1 year, 2 months

1
0
0 0

Re: [Linaro-TCWG-CI] 2 patches in binutils: FAIL: 694 regressions on aarch64

by Christophe Lyon

On Tue, 5 Mar 2024 at 21: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 binutils_check master-aarch64 after: > > | 2 patches in binutils > | Patchwork URL: https://patchwork.sourceware.org/patch/86798 > | 0fe0a00e217 aarch64: Add support for SVE ADDPT, SUBPT, MADPT, MLAPT instructions > | b9319f64d9a aarch64: Add support for (M)ADDPT and (M)SUBPT instructions > | ... applied on top of baseline commit: > | f08311ceb1b gdb/testsuite: fix duplicate test names in gdb.trace/circ.exp > > FAIL: 694 regressions > Hi Yury, Please consider this notification as a false alarm: our precommit CI does not regenerate files such as aarch64-*-2.c, as required by your patches, thus leading to the tests failures reported here. You may have seen the discussion I started a few days ago about --enable-maintainer-mode being broken. Thanks, Christophe > regressions.sum: > === binutils tests === > > Running binutils:binutils-all/aarch64/aarch64.exp ... > FAIL: Check if efi app format is recognized > FAIL: Disassembler detects unallocated instruction encodings. > === gas tests === > > Running gas:gas/aarch64/aarch64.exp ... > FAIL: AArch64 Bignums in Literal Pool (PR 16688) > FAIL: AArch64 Mapping Symbols > ... and 718 more entries > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/116… > The full lists of regressions and progressions as well as configure and make commands are in > - https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/116… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/116… > > 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/116… > Reference build : https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-build/838/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, 2 months

2
1
0 0

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

by Christophe Lyon

Hi Patrick, This report can be considered as a false alarm: the errors were already present in the baseline, but the ICE line number changed since your patch modified the code in the file where the ICE occurs. That being said, I've noticed another report saying that your patch broke bootstrap on i686. Thanks, Christophe On Sat, 2 Mar 2024 at 20:38, <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-1168 , 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-9268-g574fd1f17f1 > | Author: Patrick Palka <ppalka(a)redhat.com> > | Date: Fri Mar 1 17:24:15 2024 -0500 > | > | c++/modules: depending local enums [PR104919, PR106009] > | > | For local enums defined in a non-template function or a function template > | instantiation it seems we neglect to make the function depend on the enum > | definition (which modules considers logically separate), which ultimately > | causes the enum definition to not be properly streamed before uses > | within the function definition are streamed. > | ... 75 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:6113) > FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2a (internal compiler error: in core_vals, at cp/module.cc:6113) > FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6113) > FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6113) > FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2a (internal compiler error: in core_vals, at cp/module.cc:6113) > FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6113) > FAIL: g++.dg/modules/xtreme-header-5_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6113) > ... and 9 more entries > > progressions.sum: > === g++ tests === > > Running g++:g++.dg/modules/modules.exp ... > FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2a (internal compiler error: in core_vals, at cp/module.cc:6114) > FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6114) > FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6114) > FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6114) > FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2a (internal compiler error: in core_vals, at cp/module.cc:6114) > FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6114) > FAIL: g++.dg/modules/xtreme-header-5_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6114) > ... and 9 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/9… > 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/9… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/9… > > 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/9… > Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/9… > > 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/574fd1f17f100c7c355ad26bc525ab5a33… > > 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/9…

1 year, 2 months

1
0
0 0

[ACTIVITY] report week ending 1 Mar

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] - code review, notably another round of the raspberry pi 4b emulation series. Reviewed and took a subset of the patches, which is enough to get a working model without PCI or ethernet. We'll work on the landing other parts, but no need to block the initial model on them. * QEMU-530 [QEMU ARMv9.5 Baseline CPU for TCG] - Started implementation of FEAT_ECV (enhanced counter virtualization); I have a preliminary set of patches which I am currently testing and hope to be able to send out early next week -- PMM

1 year, 2 months

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-19-init-3481-g8c2ae42b3e1c: Failure on aarch64

by Nathan Chancellor

On Wed, Feb 28, 2024 at 02:47:11PM +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-1153 , please let us know if you are looking at the problem and/or when you have a fix. > > In CI config tcwg_kernel/llvm-master-aarch64-lts-allyesconfig after: > > | commit llvmorg-19-init-3481-g8c2ae42b3e1c > | Author: Kupa-Martin <84517188+Kupa-Martin(a)users.noreply.github.com> > | Date: Tue Feb 27 11:58:59 2024 -0300 > | > | [Clang][Sema] Fix missing warning when comparing mismatched enums in … (#81418) > | > | …C mode > | > | Factored logic from `CheckImplicitConversion` into new methods > | `Expr::getEnumConstantDecl` and `Expr::getEnumCoercedType` for use in > | `checkEnumArithmeticConversions`. > | ... 2 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: > 37 > > From > # reset_artifacts: > -10 > # build_abe binutils: > -9 > # build_kernel_llvm: > -5 > # build_abe qemu: > -2 > # linux_n_obj: > 22291 > > The configuration of this build is: > CI config tcwg_kernel/llvm-master-aarch64-lts-allyesconfig > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-lts-allyesconfig… > Reference build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-lts-allyesconfig… > > Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > > Full commit : https://github.com/llvm/llvm-project/commit/8c2ae42b3e1c6aa7c18f873edcebff7… > > List of configurations that regressed due to this commit : > * tcwg_kernel > ** llvm-master-aarch64-lts-allyesconfig > *** Failure > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > *** https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-lts-allyesconfig… Thanks a lot for the report, this is expected with that change. How we want to handle this in the kernel is currently under discussion at https://github.com/ClangBuiltLinux/linux/issues/2002. Cheers, Nathan

1 year, 2 months

1
0
0 0

Re: [Linaro-TCWG-CI] 6 patches in binutils: FAIL: 1 regressions on aarch64

by Jan Beulich

On 23.02.2024 15: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. So: The specific failure observed makes me guess that in the course of building generated files (opcodes/aarch64-*-2.c) aren't re-generated. If this is indeed the case, sending out such unsolicited emails (I've had a 2nd one in the meantime, for whatever reason) is a waste of everybody's time, even more so when not clearly indicating that fact, such that - quoting above - it is possible "within minutes" to understand what's going on / wrong. IOW - unless clarified I'm going to assume that the report here is a false negative. Jan > In binutils_check master-aarch64 after: > > | 6 patches in binutils > | Patchwork URL: https://patchwork.sourceware.org/patch/86276 > | 2d039d3b147 gas/NEWS: drop mention of Arm64's SVE2.1 and SME2.1 > | 38eca7294bd Arm64: correct SVE2.1 ld2q (scalar plus scalar) > | cb804986590 Arm64: correct SVE2.1 ld{3,4}q / st{3,4}q (scalar plus immediate) > | edaf01ca3b4 Arm64: check tied operand specifier in aarch64-gen > | 006ce007bc8 Arm64: check matching operands for predicated B16B16 insns > | ... and 1 more patches in binutils > | ... applied on top of baseline commit: > | e346d50a891 x86: rename vec_encoding and vex_encoding_* > > FAIL: 1 regressions > > regressions.sum: > === gas tests === > > Running gas:gas/aarch64/aarch64.exp ... > FAIL: Test of SVE2.1 instructions > > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/109… > The full lists of regressions and progressions as well as configure and make commands are in > - https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/109… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/109… > > 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/109… > Reference build : https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-build/797/art…

1 year, 2 months

2
3
0 0

[ACTIVITY] report week ending 23 Feb

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] - code review - finished and sent out for review the patchset that provides a 3-phase-reset version of qemu_register_reset() - The MSYS2 project are dropping their support for 32-bit Windows, which affects QEMU because we use them for our "test build on Windows" CI jobs. This prompted us to drop our 32-bit Windows host support (which conveniently we'd already deprecated last year). Sent out patches to drop the CI jobs, document that it's not a supported platform, etc. thanks -- PMM

1 year, 2 months

1
0
0 0

llvm lldb-aarch64-windows builder failing

by Ted Woodward

I apologize if this is the wrong email for this report. I got it from the "Worker" tab on a build on https://lab.llvm.org/buildbot/#/builders/219 . The build is failing at the build step. It's trying to run: ninja ^"^" ^"^" which is erroring out with ninja: error: empty path https://lab.llvm.org/buildbot/#/builders/219/builds/9644/steps/4/logs/stdio Ted

1 year, 2 months

2
1
0 0

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

by Tiezhu Yang

On 02/21/2024 03:52 AM, ci_notify(a)linaro.org wrote: > If you can't get what you need from our CI within minutes, let us know and we will be happy to help. We can see "Operation not permitted" in the log info, please try one of the following processes to test: (1) set ptrace_scope as 0 $ echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope $ make check-gdb TESTS="gdb.threads/attach-many-short-lived-threads.exp" (2) use sudo $ sudo make check-gdb TESTS="gdb.threads/attach-many-short-lived-threads.exp" Thanks, Tiezhu

1 year, 2 months

2
3
0 0

Re: [Linaro-TCWG-CI] gcc-14-9028-g7f3d900684a: FAIL: 1 regressions: 1 progressions on aarch64

by Jonathan Wakely

On Fri, 16 Feb 2024 at 19:03, <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-1155 , please let us know if you are looking at the problem and/or when you have a fix. Reported as https://gcc.gnu.org/PR113961 and fixed. > In gcc_check master-aarch64 after: > > | commit gcc-14-9028-g7f3d900684a > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Wed Feb 7 11:31:10 2024 +0000 > | > | libstdc++: Fix FAIL: 26_numerics/random/pr60037-neg.cc [PR113931] > | > | PR libstdc++/87744 > | PR libstdc++/113931 > | > | libstdc++-v3/ChangeLog: > | > | ... 2 lines of the commit log omitted. > > FAIL: 1 regressions: 1 progressions > > regressions.sum: > === libstdc++ tests === > > Running libstdc++:libstdc++-dg/conformance.exp ... > FAIL: 26_numerics/random/pr60037-neg.cc -std=gnu++17 (test for errors, line 3350) > > > progressions.sum: > === libstdc++ tests === > > Running libstdc++:libstdc++-dg/conformance.exp ... > FAIL: 26_numerics/random/pr60037-neg.cc -std=gnu++17 (test for errors, line 271) > > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1615/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/1615/artifac… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1615/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/1615/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1614/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/7f3d900684ad989164114f25eb46a33871… > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-aarch64 > *** FAIL: 1 regressions: 1 progressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1615/artifac…

1 year, 2 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-14-8998-gc9ce332b557: FAIL: 2 regressions on aarch64

by Jonathan Wakely

On Thu, 15 Feb 2024 at 21:31, <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-1154 , please let us know if you are looking at the problem and/or when you have a fix. Also reported as https://gcc.gnu.org/PR113931 and now fixed. > > In gcc_check master-aarch64 after: > > | commit gcc-14-8998-gc9ce332b557 > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Wed Feb 7 11:31:10 2024 +0000 > | > | libstdc++: Use 128-bit arithmetic for std::linear_congruential_engine [PR87744] > | > | For 32-bit targets without __int128 we need to implement the LCG > | transition function by hand using 64-bit types. > | > | We can also slightly simplify the __mod function by using if-constexpr > | unconditionally, disabling -Wc++17-extensions warnings with diagnostic > | ... 13 lines of the commit log omitted. > > FAIL: 2 regressions > > regressions.sum: > === libstdc++ tests === > > Running libstdc++:libstdc++-dg/conformance.exp ... > FAIL: 26_numerics/random/pr60037-neg.cc -std=gnu++17 (test for errors, line 271) > FAIL: 26_numerics/random/pr60037-neg.cc -std=gnu++17 (test for excess errors) > > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1609/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/1609/artifac… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1609/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/1609/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1608/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/c9ce332b557bb95987d038d98ea929cdfd… > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-aarch64 > *** FAIL: 2 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/1609/artifac…

1 year, 2 months

1
0
0 0

Fwd: [Linaro-TCWG-CI] glibc patch #85585: FAIL: 1 regressions on arm

by H.J. Lu

FAIL: elf/tst-gnu2-tls2 indicates that your _dl_tlsdesc_dynamic may not preserve all caller-saved registers. Please find out how the test fails. H.J. ---------- Forwarded message --------- From: <ci_notify(a)linaro.org> Date: Wed, Feb 14, 2024 at 3:50 PM Subject: [Linaro-TCWG-CI] glibc patch #85585: FAIL: 1 regressions on arm To: <hjl.tools(a)gmail.com> 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 glibc_check master-arm after: | glibc patch https://patchwork.sourceware.org/patch/85585 | Author: H.J. Lu <hjl.tools(a)gmail.com> | Date: Sun Feb 11 19:19:49 2024 -0800 | | x86-64: Update _dl_tlsdesc_dynamic to preserve vector registers | | Compiler generates the following instruction sequence for GNU2 dynamic | TLS access: | | leaq tls_var@TLSDESC(%rip), %rax | call *tls_var@TLSCALL(%rax) | ... 13 lines of the commit log omitted. | ... applied on top of baseline commit: | dbae3a3940 trivial doc fix: remove weird phrase "syscall takes zero to five arguments" FAIL: 1 regressions regressions.sum: === glibc tests === Running glibc:elf ... FAIL: elf/tst-gnu2-tls2 You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/1460/artif… The full lists of regressions and progressions as well as configure and make commands are in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/1460/artif… The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/1460/artif… 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-precommit/1460/artif… Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/953/artifact/a… -- H.J.

1 year, 2 months

3
7
0 0

Re: [Linaro-TCWG-CI] glibc patch #85772: FAIL: 1 regressions on aarch64

by H.J. Lu

On Thu, Feb 15, 2024 at 11:36 AM <ci_notify(a)linaro.org> wrote: > > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > In glibc_check master-aarch64 after: > > | glibc patch https://patchwork.sourceware.org/patch/85772 > | Author: H.J. Lu <hjl.tools(a)gmail.com> > | Date: Thu Feb 15 03:27:19 2024 -0800 > | > | sort-makefile-lines.py: Allow '_' in name and "^# name" > | > | '_' is used in Makefile variable names and many variables end with > | "^# name". Relax sort-makefile-lines.py to allow '_' in name and > | "^# name" as variable end. This fixes BZ #31385. > | ... applied on top of baseline commit: > | dbae3a3940 trivial doc fix: remove weird phrase "syscall takes zero to five arguments" > > FAIL: 1 regressions > > regressions.sum: > === glibc tests === > > Running glibc:. ... > FAIL: lint-makefiles > > > Should be fixed now. -- H.J.

1 year, 2 months

1
0
0 0

[ACTIVITY] report week ending 15 Feb

by Peter Maydell

Progress (short week, 3 days): * UM-2 [QEMU upstream maintainership] - various bits of cleanup and maintainer stuff - working on a 3-phase-reset-aware equivalent to qemu_register_reset(): have some basically working code, need to tidy it up and look for where the changes it makes to reset ordering might break things - sent out an email proposing that we deprecate-and-drop the pxa2xx, omap and strongarm boards. This has at least produced a useful conversation that's clarified which of these models people are using as part of their Linux kernel testing or development process. I'd still like to drop some of them if we can, though... -- PMM

1 year, 2 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc patch #85713: FAIL: 19 regressions on arm

by Maxim Kuvyrkov

Hi Richard, This is a false positive. We had a bit of instability in our CI yesterday, and it should be all fixed now. Thanks, -- Maxim Kuvyrkov https://www.linaro.org > On Feb 14, 2024, at 23:00, 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/85713 > | Author: Richard Biener <rguenther(a)suse.de> > | Date: Wed Feb 14 13:02:56 2024 +0100 > | > | tree-optimization/113910 - huge compile time during PTA > | > | For the testcase in PR113910 we spend a lot of time in PTA comparing > | bitmaps for looking up equivalence class members. This points to > | the very weak bitmap_hash function which effectively hashes set > | and a subset of not set bits. The following improves it by mixing > | that weak result with the population count of the bitmap, reducing > | ... 19 lines of the commit log omitted. > | ... applied on top of baseline commit: > | a032c319cb9 testsuite: gdc: Require ucn in gdc.test/runnable/mangle.d etc. [PR104739] > > FAIL: 19 regressions > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/dg.exp ... > FAIL: c-c++-common/pr44832.c -std=gnu++17 (test for excess errors) > FAIL: c-c++-common/pr44832.c -std=gnu++98 (test for excess errors) > FAIL: g++.dg/opt/pr100541-2.C -std=gnu++14 (test for excess errors) > FAIL: g++.dg/opt/pr100541-2.C -std=gnu++17 (test for excess errors) > FAIL: g++.dg/opt/pr100541-2.C -std=gnu++20 (test for excess errors) > > Running g++:g++.dg/pch/pch.exp ... > ... and 29 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/6118/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/6118/artifac… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/6118/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/6118/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1717/artifact/ar…

1 year, 3 months

1
0
0 0

[Linaro-TCWG-CI] binutils-2_41-release-2297-g313f04b6edc: 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-1153 , please let us know if you are looking at the problem and/or when you have a fix. In binutils_check master-arm after: | commit binutils-2_41-release-2297-g313f04b6edc | Author: Alan Modra <amodra(a)gmail.com> | Date: Thu Feb 15 19:03:07 2024 +1030 | | Re: elf_backend_finish_dynamic_symbol returning false | | I didn't examine ld testsuite logs properly after cf95b909e2c2. | Replacing one of the "return false" with BFD_ASSERT in | finish_dynamic_symbol was wrong as it causes segmentation faults on | testcases expected to fail. Revert those changes and instead make | a bfd_final_link failure noisy. FAIL: 1 regressions regressions.sum: === ld tests === Running ld:ld-arm/arm-elf.exp ... FAIL: non-contiguous-arm7 You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_binutils_check--master-arm-build/776/artifac… The full lists of regressions and progressions as well as configure and make commands are in - https://ci.linaro.org/job/tcwg_binutils_check--master-arm-build/776/artifac… The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_binutils_check--master-arm-build/776/artifac… 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-build/776/artifac… Reference build : https://ci.linaro.org/job/tcwg_binutils_check--master-arm-build/775/artifac… 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=313f04b6edcd0… List of configurations that regressed due to this commit : * tcwg_binutils_check ** master-arm *** FAIL: 1 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti… *** https://ci.linaro.org/job/tcwg_binutils_check--master-arm-build/776/artifac…

1 year, 3 months

1
0
0 0

Re: [Linaro-TCWG-CI] 2 patches in gdb: FAIL: 5 regressions on aarch64

by Guinevere Larsen

Hi! I just checked out this regression but I think there's something odd going on in the setup that is running the tests. When I run the test locally, the relevant part of the logs looks like this: (gdb) PASS: gdb.threads/threadcrash.exp: test_live_inferior: continue to breakpoint: running to breakpoint print $_inferior_thread_count^M $1 = 7^M (gdb) PASS: gdb.threads/threadcrash.exp: test_live_inferior: $thread_count == 7 thread apply all backtrace^M ^M < lots of GDB output > (gdb) PASS: gdb.threads/threadcrash.exp: test_live_inferior: Get thread information PASS: gdb.threads/threadcrash.exp: test_live_inferior: $unwind_fail == false PASS: gdb.threads/threadcrash.exp: test_live_inferior: $thread_count == [llength $test_list] Whereas the failed log reads like this: (gdb) PASS: gdb.threads/threadcrash.exp: test_live_inferior: continue to breakpoint: running to breakpoint print $_inferior_thread_count $1 = 7PASS: gdb.threads/threadcrash.exp: test_live_inferior: $thread_count == 7 (gdb) PASS: gdb.threads/threadcrash.exp: test_live_inferior: Get thread information PASS: gdb.threads/threadcrash.exp: test_live_inferior: $unwind_fail == false FAIL: gdb.threads/threadcrash.exp: test_live_inferior: $thread_count == [llength $test_list] thread apply all backtrace Notice how the gdb command to "apply all backtrace", which is used to create the test_list variable, happens after checking if the variable has been set correctly. I have no clue how things can get so out of sync... -- Cheers, Guinevere Larsen She/Her/Hers On 13/02/2024 17:09, ci_notify(a)linaro.org wrote: > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > In gdb_check master-aarch64 after: > > | 2 patches in gdb > | Patchwork URL: https://patchwork.sourceware.org/patch/85659 > | f687941ee52 gdb/testsuite: reduce gdb.threads/threadcrash.exp reliance on libc symbols > | 2e746d0ae56 gdb/testsuite: fix gdb.threads/threadcrash.exp on 32-bit arm targets > | ... applied on top of baseline commit: > | 7e4208a3f5d [gdb/tdep] Fix reverse execution of LDR(immediate) T4 > > FAIL: 5 regressions > > regressions.sum: > === gdb tests === > > Running gdb:gdb.threads/threadcrash.exp ... > FAIL: gdb.threads/threadcrash.exp: test_corefile: $thread_count == [llength $test_list] > FAIL: gdb.threads/threadcrash.exp: test_corefile: getting thread count (got interactive prompt) > FAIL: gdb.threads/threadcrash.exp: test_corefile: loading_corefile > FAIL: gdb.threads/threadcrash.exp: test_gcore: $thread_count == [llength $test_list] > FAIL: gdb.threads/threadcrash.exp: test_live_inferior: $thread_count == [llength $test_list] > > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gdb_check--master-aarch64-precommit/1701/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-aarch64-precommit/1701/art… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gdb_check--master-aarch64-precommit/1701/art… > > The configuration of this build is: > CI config tcwg_gdb_check master-aarch64 > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gdb_check--master-aarch64-precommit/1701/art… > Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-aarch64-build/814/artifact…

1 year, 3 months

2
4
0 0

Re: [Linaro-TCWG-CI] gcc-14-8949-g2ca373b7e8a: FAIL: 1 regressions: 11 progressions on arm

by Maxim Kuvyrkov

> On Feb 13, 2024, at 22:03, 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-1151 , please let us know if you are looking at the problem and/or when you have a fix. > > In gcc_check master-arm after: > > | commit gcc-14-8949-g2ca373b7e8a > | Author: Jakub Jelinek <jakub(a)redhat.com> > | Date: Tue Feb 13 10:33:08 2024 +0100 > | > | libgcc: Fix UB in FP_FROM_BITINT > | > | As I wrote earlier, I was seeing > | FAIL: gcc.dg/torture/bitint-24.c -O0 execution test > | FAIL: gcc.dg/torture/bitint-24.c -O2 execution test > | with the ia32 _BitInt enablement patch on i686-linux. I thought > | floatbitintxf.c was miscompiled with -O2 -march=i686 -mtune=generic, but it > | ... 34 lines of the commit log omitted. > > FAIL: 1 regressions: 11 progressions > > regressions.sum: > === gcc tests === > > Running gcc:gcc.dg/vect/vect.exp ... > FAIL: gcc.dg/vect/tsvc/vect-tsvc-s1281.c execution test Hi Jakub, The failure is due to the timeout. I'm going to investigate whether this is a legitimate failure or your change just pushed testcase execution time over the threshold. Running on tcwg-local: timeout -k 30s 330s ./vect-tsvc-s1281.exe spawn [open ...] value: inf, expected: inf timeout: the monitored command dumped core FAIL: gcc.dg/vect/tsvc/vect-tsvc-s1281.c execution test > > > progressions.sum: > === gcc tests === > > Running gcc:gcc.dg/guality/guality.exp ... > UNRESOLVED: c-c++-common/guality/Og-static-wo-1.c -O0 compilation failed to produce executable > FAIL: c-c++-common/guality/Og-static-wo-1.c -O0 (test for excess errors) > FAIL: gcc.dg/guality/pr41447-1.c -O0 execution test > > Running gcc:gcc.dg/ipa/ipa.exp ... > UNRESOLVED: gcc.dg/ipa/iinline-4.c scan-ipa-dump inline "hooray4[^\\n]*inline copy in test4" > UNRESOLVED: gcc.dg/ipa/iinline-4.c scan-ipa-dump inline "hooray1[^\\n]*inline copy in test1" > ... and 7 more entries Ignore these "progressions". We are having a bit of instability after enabling guality tests in our setup. -- Maxim Kuvyrkov https://www.linaro.org > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1710/artifact/ar… > 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-build/1710/artifact/ar… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1710/artifact/ar… > > The configuration of this build is: > CI config tcwg_gcc_check master-arm > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1710/artifact/ar… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1709/artifact/ar… > > Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://github.com/gcc-mirror/gcc/commit/2ca373b7e8adf9cc0c17aecab5e1cc6c76… > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-arm > *** FAIL: 1 regressions: 11 progressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1710/artifact/ar…

1 year, 3 months

2
1
0 0

Re: [Linaro-TCWG-CI] gcc patch #85693: FAIL: 33 regressions on arm

by Maxim Kuvyrkov

Hi Nathaniel, We enabled guality tests in our CI setup yesterday, and this is part of the fallout. Please ignore this report. Kind regards, -- Maxim Kuvyrkov https://www.linaro.org > On Feb 14, 2024, at 09:55, ci_notify(a)linaro.org wrote: > > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > In gcc_check master-arm after: > > | gcc patch https://patchwork.sourceware.org/patch/85693 > | Author: Nathaniel Shead <nathanieloshead(a)gmail.com> > | Date: Wed Feb 14 12:34:51 2024 +1100 > | > | c++: Defer emitting inline variables [PR113708] > | > | On Tue, Feb 13, 2024 at 06:08:42PM -0500, Jason Merrill wrote: > | > On 2/11/24 08:26, Nathaniel Shead wrote: > | > > > | > > Currently inline vars imported from modules aren't correctly finalised, > | > > which means that import_export_decl gets called at the end of TU > | ... 44 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 5f2cd521347 libstdc++: C++ item p2442 is version 1 only > > FAIL: 33 regressions > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/debug/dwarf2/dwarf2.exp ... > FAIL: g++.dg/debug/dwarf2/inline-var-1.C -std=gnu++17 scan-assembler-times 0x3[^\n\r]* DW_AT_inline 6 > FAIL: g++.dg/debug/dwarf2/inline-var-1.C -std=gnu++20 scan-assembler-times 0x3[^\n\r]* DW_AT_inline 6 > FAIL: g++.dg/debug/dwarf2/inline-var-3.C -std=gnu++17 scan-assembler-times 0x3[^\n\r]* DW_AT_inline 4 > FAIL: g++.dg/debug/dwarf2/inline-var-3.C -std=gnu++20 scan-assembler-times 0x3[^\n\r]* DW_AT_inline 4 > > Running g++:g++.dg/goacc/goacc.exp ... > FAIL: c-c++-common/goacc/routine-nohost-2.c -std=c++20 (test for errors, line 10) > ... and 35 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/6108/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/6108/artifac… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/6108/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/6108/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1714/artifact/ar…

1 year, 3 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc patch #85681: FAIL: 3 regressions on arm

by Maxim Kuvyrkov

Hi H.J., We enabled guality tests in our CI setup yesterday, and this is part of the fallout. Please ignore this report. Kind regards, -- Maxim Kuvyrkov https://www.linaro.org > On Feb 14, 2024, at 09:36, 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/85681 > | Author: H.J. Lu <hjl.tools(a)gmail.com> > | Date: Tue Feb 13 13:32:44 2024 -0800 > | > | x86-64: Generate push2/pop2 only if the incoming stack is 16-byte aligned > | > | Since push2/pop2 requires 16-byte stack alignment, don't generate them > | if the incoming stack isn't 16-byte aligned. > | > | gcc/ > | > | ... 12 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 5f2cd521347 libstdc++: C++ item p2442 is version 1 only > > FAIL: 3 regressions > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/guality/guality.exp ... > FAIL: g++.dg/guality/pr55665.C -O2 -flto -fno-use-linker-plugin -flto-partition=none line 23 p == 40 > > Running g++:g++.target/arm/arm.exp ... > XPASS: g++.target/arm/bfloat_cpp_typecheck.C (test for bogus messages, line 10) > XPASS: g++.target/arm/bfloat_cpp_typecheck.C (test for bogus messages, line 11) > > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/6104/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/6104/artifac… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/6104/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/6104/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1714/artifact/ar…

1 year, 3 months

1
0
0 0

RE: [Linaro-TCWG-CI] gcc patch #85687: FAIL: 3 regressions on arm

by Andrew Pinski (QUIC)

This does not make sense at all. The patch only touches aarch64 code and does NOT even touch arm code so there can't be any regressions with arm. Thanks, Andrew Pinski > -----Original Message----- > From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> > Sent: Tuesday, February 13, 2024 9:34 PM > To: Andrew Pinski (QUIC) <quic_apinski(a)quicinc.com> > Subject: [Linaro-TCWG-CI] gcc patch #85687: FAIL: 3 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/85687 > | Author: Andrew Pinski <quic_apinski(a)quicinc.com> > | Date: Tue Feb 13 15:22:32 2024 -0800 > | > | aarch64: Reword error message for mismatch guard size and probing > interval [PR90155] > | > | The error message is not clear what options are being taked about when it > says the values > | need to match; plus there is a wrong quotation dealing with the > diagnostic. > | So this changes the error message to be exactly talking about the param > options that > | are being taked about and now with the options, it needs the quoting. > | > | ... 8 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 5f2cd521347 libstdc++: C++ item p2442 is version 1 only > > FAIL: 3 regressions > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/guality/guality.exp ... > FAIL: g++.dg/guality/pr55665.C -O2 -flto -fno-use-linker-plugin -flto- > partition=none line 23 p == 40 > > Running g++:g++.target/arm/arm.exp ... > XPASS: g++.target/arm/bfloat_cpp_typecheck.C (test for bogus messages, line > 10) > XPASS: g++.target/arm/bfloat_cpp_typecheck.C (test for bogus messages, line > 11) > > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm- > precommit/6107/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/6107/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/6107/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/6107/artifact/artifacts > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm- > build/1714/artifact/artifacts

1 year, 3 months

2
1
0 0

Re: [Linaro-TCWG-CI] gcc patch #85664: FAIL: 29 regressions on arm

by Maxim Kuvyrkov

Hi Robin, Please ignore this report. We had a bit of instability in CI testing yesterday. -- Maxim Kuvyrkov https://www.linaro.org > On Feb 14, 2024, at 09:11, 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/85664 > | Author: Robin Dapp <rdapp.gcc(a)gmail.com> > | Date: Tue Feb 13 14:42:50 2024 +0100 > | > | RISC-V: Adjust vec unit-stride load/store costs. > | > | Hi, > | > | scalar loads provide offset addressing while unit-stride vector > | instructions cannot. The offset must be loaded into a general-purpose > | register before it can be used. In order to account for this, this > | ... 35 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 5f2cd521347 libstdc++: C++ item p2442 is version 1 only > > FAIL: 29 regressions > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/dg.exp ... > FAIL: g++.dg/ext/has_nothrow_copy-5.C -std=c++98 (test for excess errors) > FAIL: g++.dg/ext/is_base_of_diagnostic.C -std=c++17 (test for errors, line 13) > FAIL: g++.dg/ext/is_base_of_diagnostic.C -std=c++17 (test for warnings, line 4) > FAIL: g++.dg/ext/is_base_of_diagnostic.C -std=c++17 (test for excess errors) > FAIL: g++.dg/ext/packed4.C -std=gnu++17 execution test > FAIL: g++.dg/ext/vector27.C -std=c++17 (test for excess errors) > FAIL: g++.dg/ext/vector41.C -std=gnu++17 (test for errors, line 11) > ... and 27 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/6102/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/6102/artifac… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/6102/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/6102/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1714/artifact/ar…

1 year, 3 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-14-8948-g21de3391e4c: FAIL: 33 regressions on aarch64

by Maxim Kuvyrkov

Hi Jakub, Please ignore this. I'm going to investigate, but most likely this is due to instability of guality tests. -- Maxim Kuvyrkov https://www.linaro.org > On Feb 14, 2024, at 01: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-1152 , 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-8948-g21de3391e4c > | Author: Jakub Jelinek <jakub(a)redhat.com> > | Date: Tue Feb 13 10:32:01 2024 +0100 > | > | hwint: Fix up preprocessor conditions for GCC_PRISZ/fmt_size_t > | > | Using unsigned long long int for fmt_size_t and "ll" for GCC_PRISZ > | as broke the gengtype on i686-linux before the libiberty fix is certainly > | unexpected. size_t is there unsigned int, so expected fmt_size_t is > | unsigned int (or some other 32-bit type). > | > | ... 8 lines of the commit log omitted. > > FAIL: 33 regressions > > regressions.sum: > === gcc tests === > > Running gcc:gcc.dg/guality/guality.exp ... > FAIL: gcc.dg/guality/example.c -O1 -DPREVENT_OPTIMIZATION execution test > FAIL: gcc.dg/guality/pr43051-1.c -O1 -DPREVENT_OPTIMIZATION line 34 c == &a[0] > FAIL: gcc.dg/guality/pr43051-1.c -O1 -DPREVENT_OPTIMIZATION line 39 c == &a[0] > FAIL: gcc.dg/guality/pr43051-1.c -O2 -DPREVENT_OPTIMIZATION line 34 c == &a[0] > FAIL: gcc.dg/guality/pr43051-1.c -O2 -DPREVENT_OPTIMIZATION line 39 c == &a[0] > FAIL: gcc.dg/guality/pr43051-1.c -O2 -flto -fno-use-linker-plugin -flto-partition=none -DPREVENT_OPTIMIZATION line 34 c == &a[0] > FAIL: gcc.dg/guality/pr43051-1.c -O2 -flto -fno-use-linker-plugin -flto-partition=none -DPREVENT_OPTIMIZATION line 39 c == &a[0] > ... and 27 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/1595/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/1595/artifac… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1595/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/1595/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1592/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/21de3391e4cecfef6ad1b60772cb55616c… > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-aarch64 > *** FAIL: 33 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/1595/artifac…

1 year, 3 months

1
0
0 0

hey, i would like to know that how does linaro build its toolchain, is there any script that you use for build tool chains?

by Dhruv Tadvi

1 year, 3 months

1
0
0 0

Re: [Linaro-TCWG-CI] gdb patch #85593: Failure on arm

by Christophe Lyon

Hi Stephan, Sorry this clearly looks like a false alarm. We have enabled maintainer mode at configure time and it seems to have unexpected consequences. We've disabled it again, and will investigate what happened. Sorry for the inconvenience. Thanks, Christophe On Mon, 12 Feb 2024 at 14:31, <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_build master-arm after: > > | gdb patch https://patchwork.sourceware.org/patch/85593 > | Author: Rohr, Stephan <stephan.rohr(a)intel.com> > | Date: Mon Feb 12 04:47:40 2024 -0800 > | > | gdb: Fix assertion in 'value_primitive_field' > | > | GDB asserts that the data location of a value's field with a dynamic > | data location is resolved when fetching the field's value in > | 'value_primitive_field'. This assertion was hit because of bogus DWARF > | generated by the Intel Fortran compiler. While that compiler should fix > | the DWARF, we prefer GDB to error out here instead, e.g. to allow the > | ... 1 lines of the commit log omitted. > | ... applied on top of baseline commit: > | d4a45cd4d1c Automatic date update in version.in > > Results changed to > # reset_artifacts: > -10 > # true: > 0 > # build_abe gdb: > # FAILED > # First few build errors in logs: > # 00:02:38 make: *** [Makefile:3117: all-bfd] Error 2 > # 00:01:10 make[2]: *** [Makefile:668: BLD-POTFILES.in] Error 2 > # 00:01:10 make[2]: *** [Makefile:665: SRC-POTFILES.in] Error 2 > # 00:01:10 make[1]: *** [Makefile:1952: info-recursive] Error 1 > # 00:01:10 make: *** [Makefile:3117: all-bfd] Error 2 > > From > # reset_artifacts: > -10 > # true: > 0 > # build_abe gdb: > 1 > > The configuration of this build is: > CI config tcwg_gdb_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_gdb_build--master-arm-precommit/2108/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gdb_build--master-arm-build/742/artifact/art…

1 year, 3 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-14-8887-gd9459129ea8: FAIL: 29 regressions on master-thumb_m33_eabi

by Richard Earnshaw

I think all of these actually fall under "I suspect there are still some further issues to address here, since the framework does not correctly test that the multilibs and startup code enable alternative format; but this is still an improvement over what we had before." All the failures are execution test failures due to the fact that we don't check the available hardware/multilibs for running the test; so blindly adding options and then running the test is incorrect. But we currently lack such a test in the framework. It's also less than clear exactly what these tests are checking and which part of what they are checking that really requires the options they add. I suspect that they previously passed only by accident (they didn't really add enough flags to enable what they author thought they were checking). R. On 10/02/2024 02: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-1149 > <https://linaro.atlassian.net/browse/GNU-1149> , please let us know if > you are looking at the problem and/or when you have a fix. > > In arm-eabi cortex-m33 hard after: > > | commit gcc-14-8887-gd9459129ea8 > | Author: Richard Earnshaw <rearnsha(a)arm.com> > | Date: Mon Feb 5 17:16:45 2024 +0000 > | > | arm: testsuite: fix issues relating to fp16 alternative testing > | > | The v*_fp16_xN_1.c tests on Arm have been unstable since they were > | added. This is not a problem with the tests themselves, or > even the > | patches that were added, but with the testsuite infrastructure. It > | turned out that another set of dg- tests for fp16 were > corrupting the > | cached set of options used by the new tests, leading to running the > | ... 45 lines of the commit log omitted. > > FAIL: 29 regressions > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/dg.exp ... > FAIL: g++.dg/ext/arm-fp16/arm-fp16-ops-3.C -std=c++14 execution test > FAIL: g++.dg/ext/arm-fp16/arm-fp16-ops-3.C -std=c++17 execution test > FAIL: g++.dg/ext/arm-fp16/arm-fp16-ops-3.C -std=c++20 execution test > FAIL: g++.dg/ext/arm-fp16/arm-fp16-ops-3.C -std=c++98 execution test > FAIL: g++.dg/ext/arm-fp16/arm-fp16-ops-4.C -std=gnu++14 execution test > FAIL: g++.dg/ext/arm-fp16/arm-fp16-ops-4.C -std=gnu++17 execution test > FAIL: g++.dg/ext/arm-fp16/arm-fp16-ops-4.C -std=gnu++20 execution test > ... and 26 more entries > > You can find the failure logs in *.log.1.xz files in > - > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_eabi-b… <https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_eabi-b…> > The full lists of regressions and progressions as well as configure and > make commands are in > - > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_eabi-b… <https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_eabi-b…> > The list of [ignored] baseline and flaky failures are in > - > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_eabi-b… <https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_eabi-b…> > > The configuration of this build is: > CI config tcwg_gnu_embed_check_gcc arm-eabi -mthumb > -march=armv8-m.main+dsp+fp -mtune=cortex-m33 -mfloat-abi=hard -mfpu=auto > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_eabi-b… <https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_eabi-b…> > Reference build : > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_eabi-b… <https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_eabi-b…> > > Reproduce last good and first bad builds: > https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… <https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…> > > Full commit : > https://github.com/gcc-mirror/gcc/commit/d9459129ea8f8c3cbd6150b90e842decba… <https://github.com/gcc-mirror/gcc/commit/d9459129ea8f8c3cbd6150b90e842decba…> > > List of configurations that regressed due to this commit : > * tcwg_gnu_embed_check_gcc > ** master-thumb_m33_eabi > *** FAIL: 29 regressions > *** > https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… <https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…> > *** > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_eabi-b… <https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_eabi-b…>

1 year, 3 months

2
1
0 0

LDTS-4078 Support statement for specific Linaro Compiler versions

by Enterprise Email Handler for Jira (JEMH)

Enterprise Email Handler for Jira (JEMH) added you as a participant. View request: https://linaro-servicedesk.atlassian.net/servicedesk/customer/portal/38/LDT… Turn off this request's notifications: https://linaro-servicedesk.atlassian.net/servicedesk/customer/portal/38/LDT… This is shared with Anand Walvekar and Linaro Toolchain Mailman List ------------------------------ Powered by Jira Service Management https://www.atlassian.com/software/jira/service-desk/powered-by?utm_medium=…

1 year, 3 months

1
0
0 0

Support statement for specific Linaro Compiler versions

by Anand Walvekar

Hello, In our company we are using following version of Linaro compilers. I want to know if these versions are officially supported. If these versions are NOT supported, please let me know what is the version we may need to move to take advantage of support * LINARO-GCC - AARCH64 4.9.4 * LINARO-GCC - AARCH64 6.3.1 * LINARO-GCC 4.9 2016.2 Thanks for your help Regards/Anand

1 year, 3 months

1
0
0 0

[ACTIVITY] Report for week #6

by Philippe Mathieu-Daudé

Series: - Cleaned QEMU device model API abuses - Suggest new "wiring" step in QEMU device model - Add new qemu-system binary to experiment: - single binary - dynamic machine - heterogeneous emulation Started wiki document to share work: https://wiki.qemu.org/Dynamic_machine_and_heterogeneous_emulation_roadmap Progress: - Refactor ICH9 device to fix another QDev IRQ abuse Usual reviews - Peter's MP3R new board

1 year, 3 months

1
0
0 0

[ACTIVITY] report week ending 9 Feb

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] - code review and pullrequest wrangling + RTH's MTE fixes patchset + Some cleanup patches from Philippe + various other smaller things - sent out some minor patches: + avoid some warnings being printed during 'make check' + fix an assertion failure trying to vmsave/vmload for M-profile - a little gardening of the bug tracker * QEMU-598 [Model the MPS3-AN536 dual-Cortex-R52 FPGA image] - Finished off the loose ends and sent patchset out for review -- PMM

1 year, 3 months

1
0
0 0

RE: [Linaro-TCWG-CI] gcc-14-8499-gbad991a1c59: FAIL: 1 regressions on master-thumb_m0_eabi

by Matthieu Longo

Hi, The regression was introduced after we added a new test (rev16_2.c) in https://github.com/gcc-mirror/gcc/commit/bad991a1c5960e90c4686a9362a1258ef2…. The generated code is functionally correct, but the optimization is disabled when -mthumb is equivalent to Thumb1. The fix would not be suitable for stage 4. Instead, I opened a Jira ticket on our side to track the issue and prioritize it. In the meantime, I am going to publish a patch to mark the test as XFAIL when used with thumb1. Regards, Matthieu -----Original Message----- From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Sent: Thursday, February 1, 2024 5:10 PM To: Richard Earnshaw <Richard.Earnshaw(a)arm.com> Cc: gcc-regression(a)gcc.gnu.org; Matthieu Longo <Matthieu.Longo(a)arm.com> Subject: [Linaro-TCWG-CI] gcc-14-8499-gbad991a1c59: FAIL: 1 regressions on master-thumb_m0_eabi 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-1141 , please let us know if you are looking at the problem and/or when you have a fix. In arm-eabi cortex-m0 soft after: | commit gcc-14-8499-gbad991a1c59 | Author: Matthieu Longo <matthieu.longo(a)arm.com> | Date: Mon Jan 29 15:54:35 2024 +0000 | | arm: Add pattern for bswap + rotate -> rev16 [Bug 108933] | | The rev16 pattern was not recognised anymore as a change in the bswap | tree pass was introducing a new GIMPLE form, not recognized by the | assembly final transformation pass. | | Also, fix the output patterns for arm_rev16si_alt[12] to correctly | ... 18 lines of the commit log omitted. FAIL: 1 regressions regressions.sum: === gcc tests === Running gcc:gcc.target/arm/arm.exp ... FAIL: gcc.target/arm/rev16_2.c scan-assembler-times rev16\\tr[0-9]+, r[0-9]+ 2 You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu… The full lists of regressions and progressions as well as configure and make commands are in - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu… The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu… The configuration of this build is: CI config tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv6s-m -mtune=cortex-m0 -mfloat-abi=soft -mfpu=auto -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu… Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu… Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… Full commit : https://github.com/gcc-mirror/gcc/commit/bad991a1c5960e90c4686a9362a1258ef2… List of configurations that regressed due to this commit : * tcwg_gnu_embed_check_gcc ** master-thumb_m0_eabi *** FAIL: 1 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… *** https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu… 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, 3 months

1
0
0 0

[ACTIVITY] report week ending Feb 2

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

2
1
0 0

[Linaro-TCWG-CI] glibc-2.38.9000-382-g446e2c935a: 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-1093 , 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-382-g446e2c935a | Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> | Date: Thu Dec 21 15:59:18 2023 -0300 | | debug: Add fortify syslog tests | | It requires to be in a container tests to avoid logging bogus | information on the system. The syslog also requires to be checked in | a different process because the internal printf call will abort with | the internal syslog lock taken (which makes subsequent syslog calls | deadlock). | ... 3 lines of the commit log omitted. FAIL: 1 regressions regressions.sum: === glibc tests === Running glibc:debug ... FAIL: debug/tst-fortify-syslog === Results Summary === You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/788/artifact/a… . The full lists of regressions and progressions are in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/788/artifact/a… . The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/788/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/788/artifact/a… Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/787/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=446e2c935a174d33fa99… 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/788/artifact/a…

1 year, 4 months

1
0
0 0

[Linaro-TCWG-CI] glibc-2.38.9000-367-g667f277c78: 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-1084 , 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.38.9000-367-g667f277c78 | Author: Joe Ramsay <Joe.Ramsay(a)arm.com> | Date: Mon Dec 18 15:51:16 2023 +0000 | | aarch64: Add SIMD attributes to math functions with vector versions | | Added annotations for autovec by GCC and GFortran - this enables GCC | >= 9 to autovectorise math calls at -Ofast. | | Reviewed-by: Szabolcs Nagy <szabolcs.nagy(a)arm.com> FAIL: 1 regressions regressions.sum: === gfortran tests === Running gfortran:gfortran.dg/vect/vect.exp ... FAIL: gfortran.dg/vect/vect-8.f90 -O scan-tree-dump-times vect "vectorized 24 loops" 1 === Results Summary === 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/glibc/… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=667f277c782f4457603e… List of configurations that regressed due to this commit : * tcwg_gnu_native_check_gcc ** master-aarch64 *** FAIL: 1 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/8…

1 year, 4 months

2
1
0 0

[Linaro-TCWG-CI] gcc-14-6741-ge7dd72aefed: Failure on arm

by ci_notify＠linaro.org

Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. We track this report status in https://linaro.atlassian.net/browse/GNU-1087 , please let us know if you are looking at the problem and/or when you have a fix. In CI config tcwg_kernel/gnu-master-arm-stable-allmodconfig after: | commit gcc-14-6741-ge7dd72aefed | Author: Jakub Jelinek <jakub(a)redhat.com> | Date: Wed Dec 20 11:31:18 2023 +0100 | | c: Split -Wcalloc-transposed-args warning from -Walloc-size, -Walloc-size fixes | | The following patch changes -Walloc-size warning to no longer warn | about int *p = calloc (1, sizeof (int));, because as discussed earlier, | the size is IMNSHO sufficient in that case, for alloc_size with 2 | arguments warns if the product of the 2 arguments is insufficiently small. | | ... 37 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: 23978 # First few build errors in logs: # 00:33:29 fs/btrfs/send.c:8208:44: error: ‘kvcalloc’ sizes specified with ‘sizeof’ in the earlier argument and not in the later argument [-Werror=calloc-transposed-args] # 00:33:44 make[4]: *** [scripts/Makefile.build:243: fs/btrfs/send.o] Error 1 # 00:35:42 make[3]: *** [scripts/Makefile.build:480: fs/btrfs] Error 2 # 00:37:40 make[2]: *** [scripts/Makefile.build:480: fs] Error 2 # 00:47:05 make[1]: *** [/home/tcwg-buildslave/workspace/tcwg_kernel_1/linux/Makefile:1913: .] Error 2 # 00:47:05 make: *** [Makefile:234: __sub-make] Error 2 From # reset_artifacts: -10 # build_abe binutils: -9 # build_abe stage1: -5 # build_abe qemu: -2 # linux_n_obj: 33156 # linux build successful: all # linux boot successful: boot The configuration of this build is: CI config tcwg_kernel/gnu-master-arm-stable-allmodconfig -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-arm-stable-allmodconfig-b… Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-arm-stable-allmodconfig-b… Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… Full commit : https://github.com/gcc-mirror/gcc/commit/e7dd72aefed851d11655aa301d6e394ec9… List of configurations that regressed due to this commit : * tcwg_kernel ** gnu-master-arm-stable-allmodconfig *** Failure *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… *** https://ci.linaro.org/job/tcwg_kernel--gnu-master-arm-stable-allmodconfig-b…

1 year, 4 months

2
1
0 0

[Linaro-TCWG-CI] newlib-4.3.0-378-gf81bf08f7: Failure on master-thumb_v8a_hard_eabi

by ci_notify＠linaro.org

Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. We track this report status in https://linaro.atlassian.net/browse/GNU-1082 , please let us know if you are looking at the problem and/or when you have a fix. In arm-eabi thumb v8-a hard after: | commit newlib-4.3.0-378-gf81bf08f7 | Author: Jeff Johnston <jjohnstn(a)redhat.com> | Date: Tue Dec 19 13:58:12 2023 -0500 | | Add generated files for Revert patch Results changed to # reset_artifacts: -10 # true: 0 # build_abe binutils: 1 # build_abe stage1 -- --set gcc_override_configure=--disable-multilib --set gcc_override_configure=--with-mode=thumb --set gcc_override_configure=--with-arch=armv8-a+simd --set gcc_override_configure=--with-fpu=crypto-neon-fp-armv8 --set gcc_override_configure=--with-float=hard: 2 # build_abe newlib: # FAILED # build_abe stage2 -- --set gcc_override_configure=--disable-multilib --set gcc_override_configure=--with-mode=thumb --set gcc_override_configure=--with-arch=armv8-a+simd --set gcc_override_configure=--with-fpu=crypto-neon-fp-armv8 --set gcc_override_configure=--with-float=hard: # build_abe gdb: # build_abe qemu: # First few build errors in logs: # 00:00:27 /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/snapshots/newlib.git~master/libgloss/arm/arm.h:32:10: fatal error: arm-acle-compat.h: No such file or directory # 00:00:27 make[4]: *** [Makefile:2487: arm/_exit.o] Error 1 # 00:00:27 make[3]: *** [Makefile:4931: all-recursive] Error 1 # 00:00:27 make[2]: *** [Makefile:1213: all] Error 2 # 00:00:27 make[1]: *** [Makefile:9528: all-target-libgloss] Error 2 # 00:00:27 make: *** [Makefile:879: all] Error 2 # 00:00:24 /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/snapshots/newlib.git~master/libgloss/arm/arm.h:32:10: fatal error: arm-acle-compat.h: No such file or directory # 00:00:24 /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/snapshots/newlib.git~master/libgloss/arm/arm.h:32:10: fatal error: arm-acle-compat.h: No such file or directory # 00:00:24 /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/snapshots/newlib.git~master/libgloss/arm/arm.h:32:10: fatal error: arm-acle-compat.h: No such file or directory # 00:00:24 /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/snapshots/newlib.git~master/libgloss/arm/arm.h:32:10: fatal error: arm-acle-compat.h: No such file or directory # 00:00:24 /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/snapshots/newlib.git~master/libgloss/arm/arm.h:32:10: fatal error: arm-acle-compat.h: No such file or directory # 00:00:24 make[4]: *** [Makefile:5361: arm/rdpmon-crt0.o] Error 1 # 00:00:24 make[4]: *** [Makefile:5364: arm/rdimon-crt0.o] Error 1 # 00:00:24 make[4]: *** [Makefile:5367: arm/rdimon-crt0-v2m.o] Error 1 # 00:00:24 make[4]: *** [Makefile:2345: arm/crt0.o] Error 1 # 00:00:24 make[4]: *** [Makefile:2345: arm/redboot-crt0.o] Error 1 From # reset_artifacts: -10 # true: 0 # build_abe binutils: 1 # build_abe stage1 -- --set gcc_override_configure=--disable-multilib --set gcc_override_configure=--with-mode=thumb --set gcc_override_configure=--with-arch=armv8-a+simd --set gcc_override_configure=--with-fpu=crypto-neon-fp-armv8 --set gcc_override_configure=--with-float=hard: 2 # build_abe newlib: 4 # build_abe stage2 -- --set gcc_override_configure=--disable-multilib --set gcc_override_configure=--with-mode=thumb --set gcc_override_configure=--with-arch=armv8-a+simd --set gcc_override_configure=--with-fpu=crypto-neon-fp-armv8 --set gcc_override_configure=--with-float=hard: 5 # build_abe gdb: 6 # build_abe qemu: 7 The configuration of this build is: CI config tcwg_gnu_embed_build arm-eabi -mthumb -march=armv8-a+simd -mfpu=auto -mfloat-abi=hard -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_gnu_embed_build--master-thumb_v8a_hard_eabi-… Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_build--master-thumb_v8a_hard_eabi-… Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/newlib… Full commit : https://sourceware.org/git/?p=newlib-cygwin.git;a=commitdiff;h=f81bf08f7caa… List of configurations that regressed due to this commit : * tcwg_gnu_embed_build ** master-thumb_v8a_hard_eabi *** Failure *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/newlib… *** https://ci.linaro.org/job/tcwg_gnu_embed_build--master-thumb_v8a_hard_eabi-…

1 year, 4 months

2
1
0 0

[ACTIVITY] report week ending 15 Dec

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] - Working through my to-review queue and building up a target-arm queue of patches ready to go when 8.2 releases and we reopen development for 9.0 * QEMU-623 [Nested Virtualization Emulation] - The inner-kernel crash I was looking at last week goes away if the CPU has CTR_EL0.{DIC,IDC} == {1,1} to tell the guest it doesn't need to do cache maintenance. Marc Z reckons that it is likely a KVM bug. - Worked through the details of when FPU/SVE/SME access traps apply and tweaked my patches to get this right. - Added correct handling of the MTE TFSR_EL* sysregs under FEAT_NV. - I think I should be able to get patches out for review early next week. thanks -- PMM

1 year, 5 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-14-6456-gdabd94da0c7: FAIL: 4 regressions: 3 progressions on aarch64

by Christophe Lyon

Hi Jakub, Of course the CI is confused and reports regressions because after your patch there are new "FAIL" enabled since you fixed the "ERROR" cases. It sees new "FAIL" and interprets that as a regression. Thanks, Christophe On Tue, 12 Dec 2023 at 17:17, <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 track this report status in https://linaro.atlassian.net/browse/GNU-1071 , 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-6456-gdabd94da0c7 > | Author: Jakub Jelinek <jakub(a)redhat.com> > | Date: Tue Dec 12 13:07:35 2023 +0100 > | > | testsuite: Fix up test directive syntax errors > | > | I've noticed > | +ERROR: gcc.dg/gomp/pr87887-1.c: syntax error in target selector ".-4" for " dg-warning 13 "unsupported return type ‘struct S’ for ‘simd’ functions" { target aarch64*-*-* } .-4 " > | +ERROR: gcc.dg/gomp/pr87887-1.c: syntax error in target selector ".-4" for " dg-warning 13 "unsupported return type ‘struct S’ for ‘simd’ functions" { target aarch64*-*-* } .-4 " > | +ERROR: gcc.dg/gomp/pr89246-1.c: syntax error in target selector ".-4" for " dg-warning 11 "unsupported argument type ‘__int128’ for ‘simd’ functions" { target aarch64*-*-* } .-4 " > | +ERROR: gcc.dg/gomp/pr89246-1.c: syntax error in target selector ".-4" for " dg-warning 11 "unsupported argument type ‘__int128’ for ‘simd’ functions" { target aarch64*-*-* } .-4 " > | ... 9 lines of the commit log omitted. > > FAIL: 4 regressions: 3 progressions > > regressions.sum: > === gcc tests === > > Running gcc:gcc.dg/gomp/gomp.exp ... > FAIL: gcc.dg/gomp/pr87887-1.c at line 13 (test for warnings, line 9) > FAIL: gcc.dg/gomp/pr87887-1.c at line 21 (test for warnings, line 17) > FAIL: gcc.dg/gomp/pr89246-1.c at line 11 (test for warnings, line 7) > FAIL: gcc.dg/gomp/simd-clones-2.c scan-tree-dump optimized "_ZGVnN4vvva32_addit" > > === Results Summary === > > progressions.sum: > === gcc tests === > > Running gcc:gcc.dg/gomp/gomp.exp ... > ERROR: gcc.dg/gomp/pr87887-1.c: syntax error in target selector ".-4" for " dg-warning 13 "unsupported return type â€˜struct Sâ€™ for â€˜simdâ€™ functions" { target aarch64*-*-* } .-4 " > ERROR: gcc.dg/gomp/pr89246-1.c: syntax error in target selector ".-4" for " dg-warning 11 "unsupported argument type â€˜__int128â€™ for â€˜simdâ€™ functions" { target aarch64*-*-* } .-4 " > ERROR: gcc.dg/gomp/simd-clones-2.c: unmatched open quote in list for " dg-final 19 { scan-tree-dump "_ZGVnN2ua32vl_setArray" "optimized { target aarch64*-*-* } } " > > === Results Summary === > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1339/artifac… . > The full lists of regressions and progressions are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1339/artifac… . > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1339/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/1339/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1338/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/dabd94da0c78f4beb0c2c25f38ab6de2d8… > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-aarch64 > *** FAIL: 4 regressions: 3 progressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1339/artifac…

1 year, 5 months

1
0
0 0

[ACTIVITY] Report for weeks #48 #49

by Philippe Mathieu-Daudé

Progress: * QEMU-625: Reorg of include/exec/ headers - Clarified user-emulation headers - Sorted translation-related headers - Almost done with softmmu headers Obviously cleaning the icount headers revealed an issue with ARM vPMU implementation in KVM vs HVF

1 year, 5 months

1
0
0 0

[ACTIVITY] report week ending 8 Dec

by Peter Maydell

Progress: * QEMU-623 [Nested Virtualization Emulation] - Progress on debugging: fixed last week's bugs, and can now get the outer kernel to boot a middle kernel which boots an inner kernel. Unfortunately the inner kernel boot hangs during init of the PF_NETLINK subsystem, when it hits a prefetch abort due to a permissions check failure in the stage 2... - tidied up a lot of the bugfix fixup patches I had in my patchstack and merged them into the correct patches; they would be quite close to ready to send out if not for the bug I'm chasing down. -- PMM

1 year, 5 months

1
0
0 0

[Linaro-TCWG-CI] gcc-14-6259-g20214aaab6f: Failure on aarch64

by ci_notify＠linaro.org

Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. We track this report status in https://linaro.atlassian.net/browse/GNU-1064 , please let us know if you are looking at the problem and/or when you have a fix. In CI config tcwg_kernel/gnu-master-aarch64-next-defconfig after: | commit gcc-14-6259-g20214aaab6f | Author: Victor Do Nascimento <victor.donascimento(a)arm.com> | Date: Thu Nov 2 15:52:52 2023 +0000 | | aarch64: rcpc3: add Neon ACLE wrapper functions to `arm_neon.h' | | Create the necessary mappings from the ACLE-defined Neon intrinsics | names[1] to the internal builtin function names. | | [1] https://arm-software.github.io/acle/neon_intrinsics/advsimd.html | | ... 18 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: 8197 # First few build errors in logs: # 00:00:56 /home/tcwg-buildslave/workspace/tcwg_kernel_1/abe/builds/destdir/x86_64-pc-linux-gnu/lib/gcc/aarch64-linux-gnu/14.0.0/include/arm_neon.h:13474:48: error: passing argument 1 of ‘__builtin_aarch64_vec_ldap1_lanev1di’ from incompatible pointer type [-Wincompatible-pointer-types] # 00:00:56 /home/tcwg-buildslave/workspace/tcwg_kernel_1/abe/builds/destdir/x86_64-pc-linux-gnu/lib/gcc/aarch64-linux-gnu/14.0.0/include/arm_neon.h:13481:48: error: passing argument 1 of ‘__builtin_aarch64_vec_ldap1_lanev2di’ from incompatible pointer type [-Wincompatible-pointer-types] # 00:00:56 /home/tcwg-buildslave/workspace/tcwg_kernel_1/abe/builds/destdir/x86_64-pc-linux-gnu/lib/gcc/aarch64-linux-gnu/14.0.0/include/arm_neon.h:13536:40: error: passing argument 1 of ‘__builtin_aarch64_vec_stl1_lanev1di’ from incompatible pointer type [-Wincompatible-pointer-types] # 00:00:56 /home/tcwg-buildslave/workspace/tcwg_kernel_1/abe/builds/destdir/x86_64-pc-linux-gnu/lib/gcc/aarch64-linux-gnu/14.0.0/include/arm_neon.h:13543:40: error: passing argument 1 of ‘__builtin_aarch64_vec_stl1_lanev2di’ from incompatible pointer type [-Wincompatible-pointer-types] # 00:00:56 make[3]: *** [scripts/Makefile.build:243: arch/arm64/lib/xor-neon.o] Error 1 # 00:00:56 make[2]: *** [scripts/Makefile.build:480: arch/arm64/lib] Error 2 # 00:11:43 make[1]: *** [/home/tcwg-buildslave/workspace/tcwg_kernel_1/linux/Makefile:1911: .] Error 2 # 00:11:43 make: *** [Makefile:234: __sub-make] Error 2 From # reset_artifacts: -10 # build_abe binutils: -9 # build_abe stage1: -5 # build_abe qemu: -2 # linux_n_obj: 9409 # linux build successful: all # linux boot successful: boot The configuration of this build is: CI config tcwg_kernel/gnu-master-aarch64-next-defconfig -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-next-defconfig-bu… Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-next-defconfig-bu… Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… Full commit : https://github.com/gcc-mirror/gcc/commit/20214aaab6fe8d77523ef86b47248f3599… List of configurations that regressed due to this commit : * tcwg_kernel ** gnu-master-aarch64-next-defconfig *** Failure *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… *** https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-next-defconfig-bu…

1 year, 5 months

1
0
0 0

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

by Jonathan Wakely

On Thu, 7 Dec 2023 at 05:12, <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. I've already fixed this one locally. > > In gcc_check master-arm after: > > | gcc patch https://patchwork.sourceware.org/patch/81520 > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Wed Dec 6 14:18:12 2023 +0000 > | > | libstdc++: Make __gnu_debug::vector usable in constant expressions [PR109536] > | > | Any comments on this approach? > | > | -- >8 -- > | > | This makes constexpr std::vector (mostly) work in Debug Mode. All safe > | ... 73 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 3ba505c7b17 [APX NDD] Support TImode shift for NDD > > FAIL: 1 regressions > > regressions.sum: > === libstdc++ tests === > > Running libstdc++:libstdc++-dg/conformance.exp ... > FAIL: 23_containers/vector/cons/destructible_debug_neg.cc -std=gnu++17 (test for errors, line 172) > > === Results Summary === > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/5295/artifac… . > The full lists of regressions and progressions are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/5295/artifac… . > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/5295/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/5295/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1418/artifact/ar…

1 year, 5 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain