linaro-toolchain February 2024

linaro-toolchain@lists.linaro.org

22 participants
28 discussions

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…

9 months, 1 week

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

9 months, 1 week

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…

9 months, 1 week

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…

9 months, 1 week

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…

9 months, 1 week

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…

9 months, 1 week

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

9 months, 1 week

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…

9 months, 1 week

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…

9 months, 1 week

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

9 months, 1 week

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain February 2024