linaro-toolchain December 2023

linaro-toolchain@lists.linaro.org

10 participants
16 discussions

by Iain Sandoe

Hi So, I have a ci fail email, and it seems likely to be a valid complaint - but the reproduce instructions do not work on my platform (bash is not new enough) and also do not work on cfarm186 (../jenkins-scripts/jenkins-helpers.sh: line 1762: ts: command not found) For the record, the patch that is flagged as failing *was* tested on aarch64-linux-gnu (cfarm185) So, I am trying to figure out if the target is different, or some other configure argument. .. but I cannot work out the failing configure line at present - nor can I see a place to download the console log from the actual failing GCC build (which would presumably have that configure line). any help much appreciated. Iain

10 months, 1 week

Re: [Linaro-TCWG-CI] 7 patches in gcc: Failure on arm

by Lehua Ding

Hi, I received an error reported by CI for my patchs, I would like to ask how I have to reproduce it locally? I looked at the logs and didn't find the way how it compiles. Thanks in advance. On 2023/11/8 16:59, ci_notify(a)linaro.org wrote: > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > In gcc_build master-arm after: > > | 7 patches in gcc > | Patchwork URL: https://patchwork.sourceware.org/patch/79366 > | ef64c12c9f0 lra: Support subreg live range track and conflict detect > | a871f544e2b lra: Apply live_subreg df_problem to lra pass > | 6437747d6f3 ira: Add all nregs >= 2 pseudos to tracke subreg list > | 1a2da1ad5f0 ira: Support subreg copy > | 4f8d8e764e0 ira: Support subreg live range track > | ... and 2 more patches in gcc > | ... applied on top of baseline commit: > | ca281a7b971 [i386] APX: Fix ICE due to movti postreload splitter [PR112394] > > Results changed to > # reset_artifacts: > -10 > # true: > 0 > # build_abe gcc: > # FAILED > # First few build errors in logs: > # 00:03:49 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/libgcc2.c:2700:1: internal compiler error: Aborted > # 00:03:49 make[2]: *** [Makefile:505: _muldc3.o] Error 1 > # 00:03:49 make[1]: *** [Makefile:14486: all-target-libgcc] Error 2 > # 00:03:49 make: *** [Makefile:1056: all] Error 2 > # 00:03:41 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/fixed-bit.c:72:1: internal compiler error: Aborted > # 00:03:41 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/libgcc2.c:2700:1: internal compiler error: Aborted > # 00:03:41 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/fixed-bit.c:72:1: internal compiler error: Aborted > # 00:03:41 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/fixed-bit.c:72:1: internal compiler error: Aborted > # 00:03:41 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/fixed-bit.c:72:1: internal compiler error: Aborted > # 00:03:42 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/libgcc2.c:2865:1: internal compiler error: Aborted > # 00:03:42 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/fixed-bit.c:143:1: internal compiler error: Aborted > # 00:03:42 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/fixed-bit.c:143:1: internal compiler error: Aborted > # 00:03:42 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/fixed-bit.c:143:1: internal compiler error: Aborted > # 00:03:42 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/fixed-bit.c:143:1: internal compiler error: Aborted > > From > # reset_artifacts: > -10 > # true: > 0 > # build_abe gcc: > 1 > > The configuration of this build is: > CI config tcwg_gcc_build/master-arm > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gcc_build--master-arm-precommit/4076/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-arm-build/1364/artifact/ar… -- Best, Lehua (RiVAI) lehua.ding(a)rivai.ai

10 months, 1 week

Re: [Linaro-TCWG-CI] gcc patch #80969: Failure on arm

by Rainer Orth

ci_notify(a)linaro.org writes: > Dear contributor, our automatic CI has detected problems related to your > patch(es). Please find some details below. If you have any questions, > please follow up on linaro-toolchain(a)lists.linaro.org mailing list, > Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain > developer on the usual project channel. > > In gcc_build master-arm after: > > | gcc patch https://patchwork.sourceware.org/patch/80969 > | Author: Rainer Orth <ro(a)CeBiTec.Uni-Bielefeld.DE> > | Date: Wed Nov 29 15:10:00 2023 +0100 > | > | libiberty: Disable hwcaps for sha1.o > | > | This patch > | > | commit bf4f40cc3195eb7b900bf5535cdba1ee51fdbb8e > | Author: Jakub Jelinek <jakub(a)redhat.com> > | Date: Tue Nov 28 13:14:05 2023 +0100 > | ... 26 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 4c909c6ee38 In 'libgomp.c/target-simd-clone-{1,2,3}.c', restrict > | 'scan-offload-ipa-dump's to 'only_for_offload_target amdgcn-amdhsa' > > Results changed to > # reset_artifacts: > -10 > # true: > 0 > # build_abe gcc: > # FAILED > # First few build errors in logs: > # 00:02:15 gccgo: fatal error: Killed signal terminated program go1 > # 00:02:23 gcc: error: @HWCAP_CFLAGS@: linker input file not found: No such > file or directory > # 00:02:23 make[2]: *** [Makefile:1219: regex.o] Error 1 > # 00:02:23 make[1]: *** [Makefile:8370: all-libiberty] Error 2 > # 00:02:23 make: *** [Makefile:1057: all] Error 2 > # 00:01:06 gccgo: fatal error: Killed signal terminated program go1 > # 00:02:10 gcc: error: @HWCAP_CFLAGS@: linker input file not found: No such > file or directory > # 00:02:10 make[2]: *** [Makefile:776: fdmatch.o] Error 1 > # 00:02:10 gcc: error: @HWCAP_CFLAGS@: linker input file not found: No such > file or directory > # 00:02:10 make[2]: *** [Makefile:805: filedescriptor.o] Error 1 > # 00:02:10 gcc: error: @HWCAP_CFLAGS@: linker input file not found: No such > file or directory > # 00:02:10 make[2]: *** [Makefile:837: fnmatch.o] Error 1 > # 00:02:10 gcc: error: @HWCAP_CFLAGS@: linker input file not found: No such > file or directory > # 00:02:10 make[2]: *** [Makefile:817: filename_cmp.o] Error 1 > # 00:02:10 gcc: error: @HWCAP_CFLAGS@: linker input file not found: No such > file or directory > > From > # reset_artifacts: > -10 > # true: > 0 > # build_abe gcc: > 1 > > The configuration of this build is: > CI config tcwg_gcc_build master-arm > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : > https://ci.linaro.org/job/tcwg_gcc_build--master-arm-precommit/4887/artifac… > Reference build : > https://ci.linaro.org/job/tcwg_gcc_build--master-arm-build/1444/artifact/ar… > As is customary for gcc patches, this patch didn't include the generated files to simplify review. Thus, to test it in any meaningful way, one needs to run aclocal and autoconf before configuring/building. Not doing so just produces meaningless mails from the CI. Rainer

10 months, 1 week

RE: [Linaro-TCWG-CI] gcc-14-6861-g200531d5b9f: FAIL: 1 regressions on arm

by Andrew Pinski (QUIC)

> -----Original Message----- > From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> > Sent: Friday, December 29, 2023 7:40 AM > To: Andrew Pinski (QUIC) <quic_apinski(a)quicinc.com> > Cc: gcc-regression(a)gcc.gnu.org > Subject: [Linaro-TCWG-CI] gcc-14-6861-g200531d5b9f: FAIL: 1 regressions > on arm > > Dear contributor, our automatic CI has detected problems related to your > patch(es). Please find some details below. If you have any questions, please > follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg > channel, or ping your favourite Linaro toolchain developer on the usual project > channel. > > We appreciate that it might be difficult to find the necessary logs or reproduce > the issue locally. If you can't get what you need from our CI within minutes, let > us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1091 , > please let us know if you are looking at the problem and/or when you have a > fix. First I suspect this was failing before r14-6822-g01f4251b8775c8 and I just return it back to that state. The big ask I have is for reports like this, to include the exact gcc configure line that was used. In this case, is GCC configured to include neon by default? If so then the testcase needs to be updated to add an option to disable neon. If not, then someone else will need to look into why the testcase is failing. Basically, the update I did was disable vectorization on a loop which was not being vectorized before r14-6822-g01f4251b8775c8. Thanks, Andrew Pinski > > In master-arm after: > > | commit gcc-14-6861-g200531d5b9f > | Author: Andrew Pinski <quic_apinski(a)quicinc.com> > | Date: Thu Dec 28 20:26:01 2023 -0800 > | > | Fix gen-vect-26.c testcase after loops with multiple exits [PR113167] > | > | This fixes the gcc.dg/tree-ssa/gen-vect-26.c testcase by adding > | `#pragma GCC novector` in front of the loop that is doing the checking > | of the result. We only want to test the first loop to see if it can be > | vectorize. > | > | ... 9 lines of the commit log omitted. > > FAIL: 1 regressions > > regressions.sum: > === gcc tests === > > Running gcc:gcc.dg/tree-ssa/tree-ssa.exp ... > FAIL: gcc.dg/tree-ssa/gen-vect-26.c scan-tree-dump-times vect "Alignment of > access forced using peeling" 1 > > === Results Summary === > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm- > build/1147/artifact/artifacts/00-sumfiles/ . > The full lists of regressions and progressions are in > - https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm- > build/1147/artifact/artifacts/notify/ . > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm- > build/1147/artifact/artifacts/sumfiles/xfails.xfail . > > The configuration of this build is: > CI config tcwg_gnu_cross_check_gcc master-arm > > -----------------8<--------------------------8<--------------------------8<---------------- > ---------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master- > arm-build/1147/artifact/artifacts > Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc-- > master-arm-build/1146/artifact/artifacts > > Reproduce last good and first bad builds: https://git- > us.linaro.org/toolchain/ci/interesting- > commits.git/plain/gcc/sha1/200531d5b9fb99eca2b0d6b8d1e42d17641322 > 5f/tcwg_gnu_cross_check_gcc/master-arm/reproduction_instructions.txt > > Full commit : https://github.com/gcc- > mirror/gcc/commit/200531d5b9fb99eca2b0d6b8d1e42d176413225f > > List of configurations that regressed due to this commit : > * tcwg_gnu_cross_check_gcc > ** master-arm > *** FAIL: 1 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting- > commits.git/plain/gcc/sha1/200531d5b9fb99eca2b0d6b8d1e42d17641322 > 5f/tcwg_gnu_cross_check_gcc/master-arm/details.txt > *** https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm- > build/1147/artifact/artifacts

10 months, 3 weeks

[Linaro-TCWG-CI] glibc-2.38.9000-367-g667f277c78: FAIL: 1 regressions on aarch64

by ci_notify＠linaro.org

11 months, 1 week

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

by ci_notify＠linaro.org

11 months, 1 week

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

by ci_notify＠linaro.org

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

11 months, 1 week

[ACTIVITY] report week ending 15 Dec

by Peter Maydell

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

11 months, 2 weeks

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

by Christophe Lyon

Hi Jakub, Of course the CI is confused and reports regressions because after your patch there are new "FAIL" enabled since you fixed the "ERROR" cases. It sees new "FAIL" and interprets that as a regression. Thanks, Christophe On Tue, 12 Dec 2023 at 17:17, <ci_notify(a)linaro.org> wrote: > > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1071 , please let us know if you are looking at the problem and/or when you have a fix. > > In gcc_check master-aarch64 after: > > | commit gcc-14-6456-gdabd94da0c7 > | Author: Jakub Jelinek <jakub(a)redhat.com> > | Date: Tue Dec 12 13:07:35 2023 +0100 > | > | testsuite: Fix up test directive syntax errors > | > | I've noticed > | +ERROR: gcc.dg/gomp/pr87887-1.c: syntax error in target selector ".-4" for " dg-warning 13 "unsupported return type ‘struct S’ for ‘simd’ functions" { target aarch64*-*-* } .-4 " > | +ERROR: gcc.dg/gomp/pr87887-1.c: syntax error in target selector ".-4" for " dg-warning 13 "unsupported return type ‘struct S’ for ‘simd’ functions" { target aarch64*-*-* } .-4 " > | +ERROR: gcc.dg/gomp/pr89246-1.c: syntax error in target selector ".-4" for " dg-warning 11 "unsupported argument type ‘__int128’ for ‘simd’ functions" { target aarch64*-*-* } .-4 " > | +ERROR: gcc.dg/gomp/pr89246-1.c: syntax error in target selector ".-4" for " dg-warning 11 "unsupported argument type ‘__int128’ for ‘simd’ functions" { target aarch64*-*-* } .-4 " > | ... 9 lines of the commit log omitted. > > FAIL: 4 regressions: 3 progressions > > regressions.sum: > === gcc tests === > > Running gcc:gcc.dg/gomp/gomp.exp ... > FAIL: gcc.dg/gomp/pr87887-1.c at line 13 (test for warnings, line 9) > FAIL: gcc.dg/gomp/pr87887-1.c at line 21 (test for warnings, line 17) > FAIL: gcc.dg/gomp/pr89246-1.c at line 11 (test for warnings, line 7) > FAIL: gcc.dg/gomp/simd-clones-2.c scan-tree-dump optimized "_ZGVnN4vvva32_addit" > > === Results Summary === > > progressions.sum: > === gcc tests === > > Running gcc:gcc.dg/gomp/gomp.exp ... > ERROR: gcc.dg/gomp/pr87887-1.c: syntax error in target selector ".-4" for " dg-warning 13 "unsupported return type â€˜struct Sâ€™ for â€˜simdâ€™ functions" { target aarch64*-*-* } .-4 " > ERROR: gcc.dg/gomp/pr89246-1.c: syntax error in target selector ".-4" for " dg-warning 11 "unsupported argument type â€˜__int128â€™ for â€˜simdâ€™ functions" { target aarch64*-*-* } .-4 " > ERROR: gcc.dg/gomp/simd-clones-2.c: unmatched open quote in list for " dg-final 19 { scan-tree-dump "_ZGVnN2ua32vl_setArray" "optimized { target aarch64*-*-* } } " > > === Results Summary === > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1339/artifac… . > The full lists of regressions and progressions are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1339/artifac… . > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1339/artifac… . > > The configuration of this build is: > CI config tcwg_gcc_check master-aarch64 > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1339/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1338/artifac… > > Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://github.com/gcc-mirror/gcc/commit/dabd94da0c78f4beb0c2c25f38ab6de2d8… > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-aarch64 > *** FAIL: 4 regressions: 3 progressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1339/artifac…

11 months, 2 weeks

[ACTIVITY] Report for weeks #48 #49

by Philippe Mathieu-Daudé

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

11 months, 2 weeks

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain December 2023