- linaro-toolchain - lists.linaro.org

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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain