Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
We track this report status in https://linaro.atlassian.net/browse/GNU-1087 , please let us know if you are looking at the problem and/or when you have a fix.
In CI config tcwg_kernel/gnu-master-arm-stable-allmodconfig after:
| commit gcc-14-6741-ge7dd72aefed
| Author: Jakub Jelinek <jakub(a)redhat.com>
| Date: Wed Dec 20 11:31:18 2023 +0100
|
| c: Split -Wcalloc-transposed-args warning from -Walloc-size, -Walloc-size fixes
|
| The following patch changes -Walloc-size warning to no longer warn
| about int *p = calloc (1, sizeof (int));, because as discussed earlier,
| the size is IMNSHO sufficient in that case, for alloc_size with 2
| arguments warns if the product of the 2 arguments is insufficiently small.
|
| ... 37 lines of the commit log omitted.
Results changed to
# reset_artifacts:
-10
# build_abe binutils:
-9
# build_abe stage1:
-5
# build_abe qemu:
-2
# linux_n_obj:
23978
# First few build errors in logs:
# 00:33:29 fs/btrfs/send.c:8208:44: error: ‘kvcalloc’ sizes specified with ‘sizeof’ in the earlier argument and not in the later argument [-Werror=calloc-transposed-args]
# 00:33:44 make[4]: *** [scripts/Makefile.build:243: fs/btrfs/send.o] Error 1
# 00:35:42 make[3]: *** [scripts/Makefile.build:480: fs/btrfs] Error 2
# 00:37:40 make[2]: *** [scripts/Makefile.build:480: fs] Error 2
# 00:47:05 make[1]: *** [/home/tcwg-buildslave/workspace/tcwg_kernel_1/linux/Makefile:1913: .] Error 2
# 00:47:05 make: *** [Makefile:234: __sub-make] Error 2
From
# reset_artifacts:
-10
# build_abe binutils:
-9
# build_abe stage1:
-5
# build_abe qemu:
-2
# linux_n_obj:
33156
# linux build successful:
all
# linux boot successful:
boot
The configuration of this build is:
CI config tcwg_kernel/gnu-master-arm-stable-allmodconfig
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-arm-stable-allmodconfig-b…
Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-arm-stable-allmodconfig-b…
Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
Full commit : https://github.com/gcc-mirror/gcc/commit/e7dd72aefed851d11655aa301d6e394ec9…
List of configurations that regressed due to this commit :
* tcwg_kernel
** gnu-master-arm-stable-allmodconfig
*** Failure
*** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
*** https://ci.linaro.org/job/tcwg_kernel--gnu-master-arm-stable-allmodconfig-b…
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-…
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
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…
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
Progress:
* QEMU-623 [Nested Virtualization Emulation]
- Progress on debugging: fixed last week's bugs, and can now get
the outer kernel to boot a middle kernel which boots an inner
kernel. Unfortunately the inner kernel boot hangs during init of the
PF_NETLINK subsystem, when it hits a prefetch abort due to a
permissions check failure in the stage 2...
- tidied up a lot of the bugfix fixup patches I had in my patchstack
and merged them into the correct patches; they would be quite close
to ready to send out if not for the bug I'm chasing down.
-- PMM
Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
We track this report status in https://linaro.atlassian.net/browse/GNU-1064 , please let us know if you are looking at the problem and/or when you have a fix.
In CI config tcwg_kernel/gnu-master-aarch64-next-defconfig after:
| commit gcc-14-6259-g20214aaab6f
| Author: Victor Do Nascimento <victor.donascimento(a)arm.com>
| Date: Thu Nov 2 15:52:52 2023 +0000
|
| aarch64: rcpc3: add Neon ACLE wrapper functions to `arm_neon.h'
|
| Create the necessary mappings from the ACLE-defined Neon intrinsics
| names[1] to the internal builtin function names.
|
| [1] https://arm-software.github.io/acle/neon_intrinsics/advsimd.html
|
| ... 18 lines of the commit log omitted.
Results changed to
# reset_artifacts:
-10
# build_abe binutils:
-9
# build_abe stage1:
-5
# build_abe qemu:
-2
# linux_n_obj:
8197
# First few build errors in logs:
# 00:00:56 /home/tcwg-buildslave/workspace/tcwg_kernel_1/abe/builds/destdir/x86_64-pc-linux-gnu/lib/gcc/aarch64-linux-gnu/14.0.0/include/arm_neon.h:13474:48: error: passing argument 1 of ‘__builtin_aarch64_vec_ldap1_lanev1di’ from incompatible pointer type [-Wincompatible-pointer-types]
# 00:00:56 /home/tcwg-buildslave/workspace/tcwg_kernel_1/abe/builds/destdir/x86_64-pc-linux-gnu/lib/gcc/aarch64-linux-gnu/14.0.0/include/arm_neon.h:13481:48: error: passing argument 1 of ‘__builtin_aarch64_vec_ldap1_lanev2di’ from incompatible pointer type [-Wincompatible-pointer-types]
# 00:00:56 /home/tcwg-buildslave/workspace/tcwg_kernel_1/abe/builds/destdir/x86_64-pc-linux-gnu/lib/gcc/aarch64-linux-gnu/14.0.0/include/arm_neon.h:13536:40: error: passing argument 1 of ‘__builtin_aarch64_vec_stl1_lanev1di’ from incompatible pointer type [-Wincompatible-pointer-types]
# 00:00:56 /home/tcwg-buildslave/workspace/tcwg_kernel_1/abe/builds/destdir/x86_64-pc-linux-gnu/lib/gcc/aarch64-linux-gnu/14.0.0/include/arm_neon.h:13543:40: error: passing argument 1 of ‘__builtin_aarch64_vec_stl1_lanev2di’ from incompatible pointer type [-Wincompatible-pointer-types]
# 00:00:56 make[3]: *** [scripts/Makefile.build:243: arch/arm64/lib/xor-neon.o] Error 1
# 00:00:56 make[2]: *** [scripts/Makefile.build:480: arch/arm64/lib] Error 2
# 00:11:43 make[1]: *** [/home/tcwg-buildslave/workspace/tcwg_kernel_1/linux/Makefile:1911: .] Error 2
# 00:11:43 make: *** [Makefile:234: __sub-make] Error 2
From
# reset_artifacts:
-10
# build_abe binutils:
-9
# build_abe stage1:
-5
# build_abe qemu:
-2
# linux_n_obj:
9409
# linux build successful:
all
# linux boot successful:
boot
The configuration of this build is:
CI config tcwg_kernel/gnu-master-aarch64-next-defconfig
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-next-defconfig-bu…
Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-next-defconfig-bu…
Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
Full commit : https://github.com/gcc-mirror/gcc/commit/20214aaab6fe8d77523ef86b47248f3599…
List of configurations that regressed due to this commit :
* tcwg_kernel
** gnu-master-aarch64-next-defconfig
*** Failure
*** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
*** https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-next-defconfig-bu…
On Thu, 7 Dec 2023 at 05:12, <ci_notify(a)linaro.org> wrote:
>
> Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
I've already fixed this one locally.
>
> In gcc_check master-arm after:
>
> | gcc patch https://patchwork.sourceware.org/patch/81520
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Wed Dec 6 14:18:12 2023 +0000
> |
> | libstdc++: Make __gnu_debug::vector usable in constant expressions [PR109536]
> |
> | Any comments on this approach?
> |
> | -- >8 --
> |
> | This makes constexpr std::vector (mostly) work in Debug Mode. All safe
> | ... 73 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 3ba505c7b17 [APX NDD] Support TImode shift for NDD
>
> FAIL: 1 regressions
>
> regressions.sum:
> === libstdc++ tests ===
>
> Running libstdc++:libstdc++-dg/conformance.exp ...
> FAIL: 23_containers/vector/cons/destructible_debug_neg.cc -std=gnu++17 (test for errors, line 172)
>
> === Results Summary ===
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/5295/artifac… .
> The full lists of regressions and progressions are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/5295/artifac… .
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/5295/artifac… .
>
> The configuration of this build is:
> CI config tcwg_gcc_check master-arm
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/5295/artifac…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1418/artifact/ar…
Hello Tamar,
It looks like this failure happens because qemu-aarch64 segfaults when
trying to run the testcase binary:
Running on qemu: timeout -k 30s 330s setarch x86_64 -R qemu-aarch64 -cpu any -R 0 -L /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/aarch64-linux-gnu/libc ./mask_struct_load_3_run.exe
spawn [open ...]
timeout: the monitored command dumped core
FAIL: gcc.target/aarch64/sve/mask_struct_load_3_run.c execution test
Which would be a QEMU bug. I'm working on reproducing it and will report
there if appropriate.
However, our CI also found some size and performance regressions with
this commit, as detailed in https://linaro.atlassian.net/browse/GNU-1040:
- tcwg_bmk-code_size-cpu2017fast
- gnu-aarch64-master-O2: grew in size by 3% - 508.namd_r
- gnu-aarch64-master-O2_LTO: grew in size by 2% - 508.namd_r
- tcwg_bmk-code_size-spec2k6
- gnu-aarch64-master-O2: grew in size by 2% - 447.dealII
- gnu-aarch64-master-Os: grew in size by 2% - 456.hmmer
- tcwg_bmk-code_speed-cpu2017rate
- gnu-aarch64-master-O2: slowed down by 5% - 519.lbm_r
- gnu-aarch64-master-O3: slowed down by 5% - 519.lbm_r
- tcwg_bmk-fujitsu_speed-cpu2017speed
- gnu-aarch64-master-O2: slowed down by 19% - 644.nab_s:[.] exp@@GLIBC_2.29
The link above has the full results.
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 master-aarch64 after:
>
> | commit gcc-14-5673-g33c2b70dbab
> | Author: Tamar Christina <tamar.christina(a)arm.com>
> | Date: Tue Nov 21 13:20:39 2023 +0000
> |
> | AArch64: Add new generic-armv8-a CPU and make it the default.
> |
> | This patch adds a new generic scheduling model "generic-armv8-a" and makes it
> | the default for all Armv8 architectures.
> |
> | -mcpu=generic and -mtune=generic is kept around for those that really want the
> | previous cost model.
> | ... 34 lines of the commit log omitted.
>
> FAIL: 1 regressions: 8 progressions
>
> regressions.sum:
> === gcc tests ===
>
> Running gcc:gcc.target/aarch64/sve/aarch64-sve.exp ...
> FAIL: gcc.target/aarch64/sve/mask_struct_load_3_run.c execution test
>
> === Results Summary ===
>
> progressions.sum:
> === gcc tests ===
>
> Running gcc:gcc.dg/vect/vect.exp ...
> FAIL: gcc.dg/vect/vect-reduc-pattern-1b-big-array.c -flto -ffat-lto-objects (test for excess errors)
> UNRESOLVED: gcc.dg/vect/vect-reduc-pattern-1b-big-array.c compilation failed to produce executable
> UNRESOLVED: gcc.dg/vect/vect-reduc-pattern-1b-big-array.c -flto -ffat-lto-objects compilation failed to produce executable
> FAIL: gcc.dg/vect/vect-reduc-pattern-1b-big-array.c (test for excess errors)
> UNRESOLVED: gcc.dg/vect/vect-reduc-pattern-1b.c compilation failed to produce executable
> UNRESOLVED: gcc.dg/vect/vect-reduc-pattern-1b.c -flto -ffat-lto-objects compilation failed to produce executable
> FAIL: gcc.dg/vect/vect-reduc-pattern-1b.c (test for excess errors)
> ... and 3 more entries
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/11… .
> The full lists of regressions and progressions are in
> - https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/11… .
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/11… .
>
> The configuration of this build is:
> CI config tcwg_gnu_cross_check_gcc master-aarch64
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/11…
> Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/11…
>
> 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/33c2b70dbabc02788caabcbc66b7baeafe…
>
> Latest bug report status : https://linaro.atlassian.net/browse/GNU-1040
>
> List of configurations that regressed due to this commit :
> * tcwg_gnu_cross_check_gcc
> ** master-aarch64
> *** FAIL: 1 regressions: 8 progressions
> *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
> *** https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/11…
--
Thiago
On Wed, 6 Dec 2023 at 06:04, <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-1063 , please let us know if you are looking at the problem and/or when you have a fix.
I think my fix for PR 112882 fixes these too.
>
> In gcc_check master-aarch64 after:
>
> | commit gcc-14-6198-g5e8a30d8b8f
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Tue Dec 5 10:22:17 2023 +0000
> |
> | libstdc++: Redefine __glibcxx_assert to work in C++23 constexpr
> |
> | The changes in r14-5979 to support unknown references in constant
> | expressions caused some test regressions. The way that __glibcxx_assert
> | is defined for constant evaluation no longer works when
> | _GLIBCXX_ASSERTIONS is defined.
> |
> | ... 40 lines of the commit log omitted.
>
> FAIL: 20 regressions
>
> regressions.sum:
> === g++ tests ===
>
> Running g++:g++.dg/dg.exp ...
> FAIL: g++.dg/warn/Winvalid-memory-model-2.C -std=gnu++17 dg-regexp 28 not found: " *inlined from [^\n
> FAIL: g++.dg/warn/Winvalid-memory-model-2.C -std=gnu++17 dg-regexp 29 not found: " *inlined from [^\n
> FAIL: g++.dg/warn/Winvalid-memory-model-2.C -std=gnu++17 dg-regexp 43 not found: " *inlined from [^\n
> FAIL: g++.dg/warn/Winvalid-memory-model-2.C -std=gnu++17 dg-regexp 44 not found: " *inlined from [^\n
> FAIL: g++.dg/warn/Winvalid-memory-model-2.C -std=gnu++17 dg-regexp 45 not found: " *inlined from [^\n
> FAIL: g++.dg/warn/Winvalid-memory-model-2.C -std=gnu++17 dg-regexp 75 not found: " *inlined from [^\n
> FAIL: g++.dg/warn/Winvalid-memory-model-2.C -std=gnu++17 dg-regexp 76 not found: " *inlined from [^\n
> ... and 15 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/1305/artifac… .
> The full lists of regressions and progressions are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1305/artifac… .
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1305/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/1305/artifac…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1304/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/5e8a30d8b8f4d7ea0a8340b46c1e0c865d…
>
> List of configurations that regressed due to this commit :
> * tcwg_gcc_check
> ** master-aarch64
> *** FAIL: 20 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/1305/
Progress:
* UM-2 [QEMU upstream maintainership]
- Sent a pullrequest for this week's rc
- Sent a patch which disables SME if SVE is disabled, since QEMU currently
asserts if you try to use that combination.
* QEMU-623 [Nested Virtualization Emulation]
- Mostly working through debugging issues in my FEAT_NV/FEAT_NV2
emulation. I can get the inner guest kernel to boot up to the point
where it tries to 'eret' and the outer kernel thinks that's an invalid
exception return. More debugging scheduled for next week...
-- PMM
Hi!
On Fri, 24 Nov 2023 at 11:41, <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_check master-aarch64 after:
>
> | commit gcc-14-5810-gcff1fa6625d
> | Author: Nathaniel Shead <nathanieloshead(a)gmail.com>
> | Date: Mon Nov 13 20:11:15 2023 +1100
> |
> | c++: Support lambdas in static template member initialisers [PR107398]
> |
> | The testcase noted in the PR fails because the context of the lambda is
> | not in namespace scope, but rather in class scope. This patch removes
> | the assertion that the context must be a namespace and ensures that
> | lambdas in class scope still get the correct merge_kind.
> |
> | ... 14 lines of the commit log omitted.
>
> FAIL: 3 regressions: 3 progressions
>
> regressions.sum:
> === g++ tests ===
>
> Running g++:g++.dg/modules/modules.exp ...
> FAIL: g++.dg/modules/xtreme-header-4_b.C -std=c++2b (internal compiler error: tree check: expected class 'type', have 'declaration' (template_decl) in get_originating_module_decl, at cp/module.cc:18659)
> FAIL: g++.dg/modules/xtreme-header-5_b.C -std=c++2b (internal compiler error: tree check: expected class 'type', have 'declaration' (template_decl) in get_originating_module_decl, at cp/module.cc:18659)
> FAIL: g++.dg/modules/xtreme-header_b.C -std=c++2b (internal compiler error: tree check: expected class 'type', have 'declaration' (template_decl) in get_originating_module_decl, at cp/module.cc:18659)
>
> === Results Summary ===
>
> progressions.sum:
> === g++ tests ===
>
> Running g++:g++.dg/modules/modules.exp ...
> FAIL: g++.dg/modules/xtreme-header-4_b.C -std=c++2b (internal compiler error: tree check: expected class 'type', have 'declaration' (template_decl) in get_originating_module_decl, at cp/module.cc:18649)
> FAIL: g++.dg/modules/xtreme-header-5_b.C -std=c++2b (internal compiler error: tree check: expected class 'type', have 'declaration' (template_decl) in get_originating_module_decl, at cp/module.cc:18649)
> FAIL: g++.dg/modules/xtreme-header_b.C -std=c++2b (internal compiler error: tree check: expected class 'type', have 'declaration' (template_decl) in get_originating_module_decl, at cp/module.cc:18649)
>
I think you can ignore this notification as a false positive:
the error was already present before your patch, but at a different
line location.
Thanks,
Christophe
> === 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/1245/artifac… .
> The full lists of regressions and progressions are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1245/artifac… .
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1245/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/1245/artifac…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1244/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/cff1fa6625d1273fcfaf473e436ba91826…
>
> Latest bug report status : https://linaro.atlassian.net/browse/GNU-1037
>
> List of configurations that regressed due to this commit :
> * tcwg_gcc_check
> ** master-aarch64
> *** FAIL: 3 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/1245/
Progress:
* UM-2 [QEMU upstream maintainership]
- Usual amount of code review and upstream pull request wrangling
* QEMU-623 [Nested Virtualization Emulation]
- Since the kernel side of KVM has decided that FEAT_NV alone is
not worth supporting, I'm moving on to implementing FEAT_NV2
rather than trying to debug whether the behaviour I've been seeing
is a bug in the kernel patchset's not-really-tested FEAT_NV handling.
- I have a code-complete implementation of FEAT_NV2. Debugging next...
-- PMM
Hi Jonathan,
It also caused same regression on x86_64:
https://gcc.gnu.org/pipermail/gcc-regression/2023-November/078617.html
Could you help verify that?
Thx,
Haochen
> -----Original Message-----
> From: Gcc-regression <gcc-regression-
> bounces+haochen.jiang=intel.com(a)gcc.gnu.org> On Behalf Of ci_notify--- via
> Gcc-regression
> Sent: Friday, November 24, 2023 6:31 AM
> To: jwakely(a)redhat.com
> Cc: ci_notify(a)linaro.org; gcc-regression(a)gcc.gnu.org
> Subject: [Linaro-TCWG-CI] gcc-14-5794-g7a6a29c455e: FAIL: 1 regressions on
> aarch64
>
> Dear contributor, our automatic CI has detected problems related to your
> patch(es). Please find some details below. If you have any questions, please
> follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg
> channel, or ping your favourite Linaro toolchain developer on the usual project
> channel.
>
> In gcc_check master-aarch64 after:
>
> | commit gcc-14-5794-g7a6a29c455e
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Tue Sep 19 13:23:13 2023 +0100
> |
> | libstdc++: Define std::ranges::to for C++23 (P1206R7) [PR111055]
> |
> | This adds the std::ranges::to functions for C++23. The rest of P1206R7
> | is not yet implemented, i.e. the new constructors taking the
> | std::from_range tag, and the new insert_range, assign_range, etc.
> member
> | functions. std::ranges::to works with the standard containers even
> | without the new constructors, so this is useful immediately.
> | ... 18 lines of the commit log omitted.
>
> FAIL: 1 regressions
>
> regressions.sum:
> === g++ tests ===
>
> Running g++:g++.dg/modules/modules.exp ...
> FAIL: g++.dg/modules/xtreme-header-2_b.C -std=c++2b (test for excess
> errors)
>
> === 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/1240/artifact/artifacts/00-sumfiles/ .
> The full lists of regressions and progressions are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-
> build/1240/artifact/artifacts/notify/ .
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-
> build/1240/artifact/artifacts/sumfiles/xfails.xfail .
>
> 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/1240/artifact/artifacts
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-
> build/1239/artifact/artifacts
>
> Reproduce last good and first bad builds: https://git-
> us.linaro.org/toolchain/ci/interesting-
> commits.git/plain/gcc/sha1/7a6a29c455e7755b501c0006e39beb4e56ec27
> 29/tcwg_gcc_check/master-aarch64/reproduction_instructions.txt
>
> Full commit : https://github.com/gcc-
> mirror/gcc/commit/7a6a29c455e7755b501c0006e39beb4e56ec2729
>
> Latest bug report status : https://linaro.atlassian.net/browse/GNU-1036
>
> List of configurations that regressed due to this commit :
> * tcwg_gcc_check
> ** master-aarch64
> *** FAIL: 1 regressions
> *** https://git-us.linaro.org/toolchain/ci/interesting-
> commits.git/plain/gcc/sha1/7a6a29c455e7755b501c0006e39beb4e56ec27
> 29/tcwg_gcc_check/master-aarch64/details.txt
> *** https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1240/
Hi Jan,
The commit also caused similar regressions on x86_64:
https://gcc.gnu.org/pipermail/gcc-regression/2023-November/078575.html
The ERROR part has been resolved on the current trunk while others haven't.
Could you help verify that?
Thx,
Haochen
> -----Original Message-----
> From: Gcc-regression <gcc-regression-
> bounces+haochen.jiang=intel.com(a)gcc.gnu.org> On Behalf Of ci_notify--- via
> Gcc-regression
> Sent: Tuesday, November 21, 2023 8:01 AM
> To: jh(a)suse.cz
> Cc: ci_notify(a)linaro.org; gcc-regression(a)gcc.gnu.org
> Subject: [Linaro-TCWG-CI] gcc-14-5628-g53ba8d66955: FAIL: 2 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.
>
> In gcc_check master-arm after:
>
> | commit gcc-14-5628-g53ba8d66955
> | Author: Jan Hubicka <jh(a)suse.cz>
> | Date: Mon Nov 20 19:35:53 2023 +0100
> |
> | inter-procedural value range propagation
> |
> | implement very basic propapgation of return value ranges from VRP
> | pass. This helps std::vector's push_back since we work out value range of
> | allocated block. This propagates only within single translation unit. I
> hoped
> | we will also do the propagation at WPA stage, but that needs more work
> on
> | ipa-cp side.
> | ... 52 lines of the commit log omitted.
>
> FAIL: 2 regressions
>
> regressions.sum:
> === gcc tests ===
>
> Running gcc:gcc.dg/dg.exp ...
> FAIL: gcc.dg/vla-1.c scan-tree-dump-times optimized " s=> i" 2
>
> Running gcc:gcc.dg/tree-ssa/tree-ssa.exp ...
> ERROR: gcc.dg/tree-ssa/return-value-range-1.c: 1: syntax error for " dg-do 1
> ling "
>
> === Results Summary ===
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-
> build/1307/artifact/artifacts/00-sumfiles/ .
> The full lists of regressions and progressions are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-
> build/1307/artifact/artifacts/notify/ .
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-
> build/1307/artifact/artifacts/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-
> build/1307/artifact/artifacts
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-
> build/1305/artifact/artifacts
>
> Reproduce last good and first bad builds: https://git-
> us.linaro.org/toolchain/ci/interesting-
> commits.git/plain/gcc/sha1/53ba8d669550d3a1f809048428b97ca607f95cf
> 5/tcwg_gcc_check/master-arm/reproduction_instructions.txt
>
> Full commit : https://github.com/gcc-
> mirror/gcc/commit/53ba8d669550d3a1f809048428b97ca607f95cf5
>
> Latest bug report status : https://linaro.atlassian.net/browse/GNU-1025
>
> List of configurations that regressed due to this commit :
> * tcwg_gcc_check
> ** master-arm
> *** FAIL: 2 regressions
> *** https://git-us.linaro.org/toolchain/ci/interesting-
> commits.git/plain/gcc/sha1/53ba8d669550d3a1f809048428b97ca607f95cf
> 5/tcwg_gcc_check/master-arm/details.txt
> *** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1307/
Hi Jonathon,
This patch also caused same regression on x86_64.
https://gcc.gnu.org/pipermail/gcc-regression/2023-November/078559.html
(Not all the regressions are caused by this commit, don't be worried)
Could you help verify that?
Thx,
Haochen
> -----Original Message-----
> From: Gcc-regression <gcc-regression-
> bounces+haochen.jiang=intel.com(a)gcc.gnu.org> On Behalf Of ci_notify--- via
> Gcc-regression
> Sent: Thursday, November 16, 2023 7:44 PM
> To: jwakely(a)redhat.com
> Cc: ci_notify(a)linaro.org; gcc-regression(a)gcc.gnu.org
> Subject: [Linaro-TCWG-CI] gcc-14-5524-gc7f6537db94: FAIL: 6 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.
>
> In gcc_check master-arm after:
>
> | commit gcc-14-5524-gc7f6537db94
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Wed Nov 15 23:02:34 2023 +0000
> |
> | libstdc++: Implement std::out_ptr and std::inout_ptr for C++23
> [PR111667]
> |
> | This implements that changes from P1132R8, including optimized paths
> for
> | std::shared_ptr and std::unique_ptr.
> |
> | For std::shared_ptr we pre-allocate a new control block in the
> | std::out_ptr_t constructor so that the destructor is non-throwing. This
> | ... 47 lines of the commit log omitted.
>
> FAIL: 6 regressions
>
> regressions.sum:
> === g++ tests ===
>
> Running g++:g++.dg/modules/modules.exp ...
> FAIL: g++.dg/modules/xtreme-header-4_b.C -std=c++2b (internal compiler
> error: tree check: expected class 'type', have 'declaration' (template_decl) in
> get_originating_module_decl, at cp/module.cc:18649)
> FAIL: g++.dg/modules/xtreme-header-4_b.C -std=c++2b (test for excess
> errors)
> FAIL: g++.dg/modules/xtreme-header-5_b.C -std=c++2b (internal compiler
> error: tree check: expected class 'type', have 'declaration' (template_decl) in
> get_originating_module_decl, at cp/module.cc:18649)
> FAIL: g++.dg/modules/xtreme-header-5_b.C -std=c++2b (test for excess
> errors)
> FAIL: g++.dg/modules/xtreme-header_b.C -std=c++2b (internal compiler
> error: tree check: expected class 'type', have 'declaration' (template_decl) in
> get_originating_module_decl, at cp/module.cc:18649)
> FAIL: g++.dg/modules/xtreme-header_b.C -std=c++2b (test for excess errors)
>
> ... and 1 more entries
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-
> build/1273/artifact/artifacts/00-sumfiles/ .
> The full lists of regressions and progressions are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-
> build/1273/artifact/artifacts/notify/ .
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-
> build/1273/artifact/artifacts/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-
> build/1273/artifact/artifacts
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-
> build/1272/artifact/artifacts
>
> Reproduce last good and first bad builds: https://git-
> us.linaro.org/toolchain/ci/interesting-
> commits.git/plain/gcc/sha1/c7f6537db94f7c6320a5a8ecaa387c9b9ce1f0ac/
> tcwg_gcc_check/master-arm/reproduction_instructions.txt
>
> Full commit : https://github.com/gcc-
> mirror/gcc/commit/c7f6537db94f7c6320a5a8ecaa387c9b9ce1f0ac
>
> Latest bug report status : https://linaro.atlassian.net/browse/GNU-1014
>
> List of configurations that regressed due to this commit :
> * tcwg_gcc_check
> ** master-arm
> *** FAIL: 6 regressions
> *** https://git-us.linaro.org/toolchain/ci/interesting-
> commits.git/plain/gcc/sha1/c7f6537db94f7c6320a5a8ecaa387c9b9ce1f0ac/
> tcwg_gcc_check/master-arm/details.txt
> *** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1273/
Hi Brendan,
This patch also caused same regression on x86_64.
https://gcc.gnu.org/pipermail/gcc-regression/2023-November/078479.html
Could you help verify that?
Thx,
Haochen
> -----Original Message-----
> From: Gcc-regression <gcc-regression-
> bounces+haochen.jiang=intel.com(a)gcc.gnu.org> On Behalf Of ci_notify--- via
> Gcc-regression
> Sent: Friday, November 10, 2023 6:11 PM
> To: jlaw(a)ventanamicro.com
> Cc: ci_notify(a)linaro.org; gcc-regression(a)gcc.gnu.org;
> bshanks(a)codeweavers.com
> Subject: [Linaro-TCWG-CI] gcc-14-5310-g879cf9ff45d: FAIL: 6 regressions on
> aarch64
>
> Dear contributor, our automatic CI has detected problems related to your
> patch(es). Please find some details below. If you have any questions, please
> follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg
> channel, or ping your favourite Linaro toolchain developer on the usual project
> channel.
>
> In gcc_check master-aarch64 after:
>
> | commit gcc-14-5310-g879cf9ff45d
> | Author: Brendan Shanks <bshanks(a)codeweavers.com>
> | Date: Thu Nov 9 21:01:07 2023 -0700
> |
> | [PATCH v3] libiberty: Use posix_spawn in pex-unix when available.
> |
> | Hi,
> |
> | This patch implements pex_unix_exec_child using posix_spawn when
> | available.
> |
> | ... 20 lines of the commit log omitted.
>
> FAIL: 6 regressions
>
> regressions.sum:
> === g++ tests ===
>
> Running g++:g++.dg/modules/modules.exp ...
> FAIL: g++.dg/modules/bad-mapper-1.C -std=c++17 at line 3 (test for errors,
> line )
> FAIL: g++.dg/modules/bad-mapper-1.C -std=c++17 (test for excess errors)
> FAIL: g++.dg/modules/bad-mapper-1.C -std=c++2a at line 3 (test for errors,
> line )
> FAIL: g++.dg/modules/bad-mapper-1.C -std=c++2a (test for excess errors)
> FAIL: g++.dg/modules/bad-mapper-1.C -std=c++2b at line 3 (test for errors,
> line )
> FAIL: g++.dg/modules/bad-mapper-1.C -std=c++2b (test for excess errors)
>
> ... and 1 more entries
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-
> build/1159/artifact/artifacts/00-sumfiles/ .
> The full lists of regressions and progressions are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-
> build/1159/artifact/artifacts/notify/ .
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-
> build/1159/artifact/artifacts/sumfiles/xfails.xfail .
>
> 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/1159/artifact/artifacts
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-
> build/1158/artifact/artifacts
>
> Reproduce last good and first bad builds: https://git-
> us.linaro.org/toolchain/ci/interesting-
> commits.git/plain/gcc/sha1/879cf9ff45d94065d89e24b71c6b27c7076ac51
> 8/tcwg_gcc_check/master-aarch64/reproduction_instructions.txt
>
> Full commit : https://github.com/gcc-
> mirror/gcc/commit/879cf9ff45d94065d89e24b71c6b27c7076ac518
>
> Latest bug report status : https://linaro.atlassian.net/browse/GNU-1000
>
> List of configurations that regressed due to this commit :
> * tcwg_gcc_check
> ** master-aarch64
> *** FAIL: 6 regressions
> *** https://git-us.linaro.org/toolchain/ci/interesting-
> commits.git/plain/gcc/sha1/879cf9ff45d94065d89e24b71c6b27c7076ac51
> 8/tcwg_gcc_check/master-aarch64/details.txt
> *** https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1159/
Hi Jan,
This patch also caused same issue on i386.
https://gcc.gnu.org/pipermail/gcc-regression/2023-November/078590.html
Could you help verify that?
Thx,
Haochen
> -----Original Message-----
> From: Gcc-regression <gcc-regression-
> bounces+haochen.jiang=intel.com(a)gcc.gnu.org> On Behalf Of ci_notify--- via
> Gcc-regression
> Sent: Wednesday, November 22, 2023 4:20 PM
> To: jh(a)suse.cz
> Cc: ci_notify(a)linaro.org; gcc-regression(a)gcc.gnu.org
> Subject: [Linaro-TCWG-CI] gcc-14-5679-g1d82fc2e682: 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.
>
> In gcc_check master-arm after:
>
> | commit gcc-14-5679-g1d82fc2e682
> | Author: Jan Hubicka <jh(a)suse.cz>
> | Date: Tue Nov 21 15:17:16 2023 +0100
> |
> | optimize std::vector::push_back
> |
> | this patch speeds up the push_back at -O3 significantly by making the
> | reallocation to be inlined by default. _M_realloc_insert is general
> | insertion that takes iterator pointing to location where the value
> | should be inserted. As such it contains code to move other entries
> around
> | that is quite large.
> | ... 23 lines of the commit log omitted.
>
> FAIL: 1 regressions
>
> regressions.sum:
> === g++ tests ===
>
> Running g++:g++.dg/dg.exp ...
> FAIL: g++.dg/opt/pr110879.C -std=gnu++98 scan-tree-dump-not optimized
> "=\\s*\\S*res_(?!\\S*_M_end_of_storage;)"
>
> === Results Summary ===
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-
> build/1318/artifact/artifacts/00-sumfiles/ .
> The full lists of regressions and progressions are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-
> build/1318/artifact/artifacts/notify/ .
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-
> build/1318/artifact/artifacts/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-
> build/1318/artifact/artifacts
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-
> build/1317/artifact/artifacts
>
> Reproduce last good and first bad builds: https://git-
> us.linaro.org/toolchain/ci/interesting-
> commits.git/plain/gcc/sha1/1d82fc2e6824bf83159389729c31a942f7b91b0
> 4/tcwg_gcc_check/master-arm/reproduction_instructions.txt
>
> Full commit : https://github.com/gcc-
> mirror/gcc/commit/1d82fc2e6824bf83159389729c31a942f7b91b04
>
> Latest bug report status : https://linaro.atlassian.net/browse/GNU-1032
>
> List of configurations that regressed due to this commit :
> * tcwg_gcc_check
> ** master-arm
> *** FAIL: 1 regressions
> *** https://git-us.linaro.org/toolchain/ci/interesting-
> commits.git/plain/gcc/sha1/1d82fc2e6824bf83159389729c31a942f7b91b0
> 4/tcwg_gcc_check/master-arm/details.txt
> *** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1318/
Hi Richard,
This commit also caused x86_64 fail in the same testcase.
https://gcc.gnu.org/pipermail/gcc-regression/2023-November/078596.html
Is this on purpose or not?
Thx,
Haochen
> -----Original Message-----
> From: Gcc-regression <gcc-regression-
> bounces+haochen.jiang=intel.com(a)gcc.gnu.org> On Behalf Of ci_notify--- via
> Gcc-regression
> Sent: Thursday, November 23, 2023 3:02 AM
> To: rguenther(a)suse.de
> Cc: ci_notify(a)linaro.org; gcc-regression(a)gcc.gnu.org
> Subject: [Linaro-TCWG-CI] gcc-14-5759-g6bf66276e3e: 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.
>
> In gcc_check master-arm after:
>
> | commit gcc-14-5759-g6bf66276e3e
> | Author: Richard Biener <rguenther(a)suse.de>
> | Date: Wed Nov 22 11:10:41 2023 +0100
> |
> | tree-optimization/112344 - wrong final value replacement
> |
> | When performing final value replacement chrec_apply that's used to
> | compute the overall effect of niters to a CHREC doesn't consider that
> | the overall increment of { -2147483648, +, 2 } doesn't fit in
> | a signed integer when the loop iterates until the value of the IV
> | of 20. The following fixes this mistake, carrying out the multiply
> | ... 8 lines of the commit log omitted.
>
> FAIL: 3 regressions
>
> regressions.sum:
> === gcc tests ===
>
> Running gcc:gcc.dg/dg.exp ...
> FAIL: gcc.dg/Wstringop-overflow-17.c (test for warnings, line 16)
> FAIL: gcc.dg/Wstringop-overflow-17.c (test for warnings, line 9)
>
> Running gcc:gcc.dg/vect/vect.exp ...
> FAIL: gcc.dg/vect/no-scevccp-noreassoc-outer-4.c scan-tree-dump-times vect
> "OUTER LOOP VECTORIZED." 1
>
> === Results Summary ===
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-
> build/1322/artifact/artifacts/00-sumfiles/ .
> The full lists of regressions and progressions are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-
> build/1322/artifact/artifacts/notify/ .
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-
> build/1322/artifact/artifacts/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-
> build/1322/artifact/artifacts
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-
> build/1321/artifact/artifacts
>
> Reproduce last good and first bad builds: https://git-
> us.linaro.org/toolchain/ci/interesting-
> commits.git/plain/gcc/sha1/6bf66276e3e41d5d92f7b7260e98b6a1116538
> 05/tcwg_gcc_check/master-arm/reproduction_instructions.txt
>
> Full commit : https://github.com/gcc-
> mirror/gcc/commit/6bf66276e3e41d5d92f7b7260e98b6a111653805
>
> Latest bug report status : https://linaro.atlassian.net/browse/GNU-1033
>
> List of configurations that regressed due to this commit :
> * tcwg_gcc_check
> ** master-arm
> *** FAIL: 3 regressions
> *** https://git-us.linaro.org/toolchain/ci/interesting-
> commits.git/plain/gcc/sha1/6bf66276e3e41d5d92f7b7260e98b6a1116538
> 05/tcwg_gcc_check/master-arm/details.txt
> *** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1322/
# TCWG CI
- Addressed Maxim's comments and submitted v4 of Abe change to always
add detected flaky tests to the flaky.xfail file, even if they are
already present in the baseline results.
- Wrote Ansible playbook to configure our bare metal machines.
- Analysed GDB on arm regressions GNU-1007 and GNU-1015.
# Misc
- Had public holiday on Wednesday.
--
Thiago
Progress (short week, 3 days):
* UM-2 [QEMU upstream maintainership]
- put together pull request for a handful of bugfixes for rc0
- fixed the FEAT_MOPS reverse-copy bug and sent a patch for it
* QEMU-292 [ARMv8.3 FEAT_NV, Nested Virtualization]
- trying to get a setup with kvmtool and a kernel with the WIP
FEAT_NV support working. I now have a setup that works when you don't
ask for the inner-guest to have EL2 support, but when you do enable
--nested it boots the inner-guest fine and then hangs at about the
point where it should be mounting the rootfs. This might be tedious
to debug...
-- PMM
Progress:
* UM-2 [QEMU upstream maintainership]
- Noticed that if the guest uses the HVC insn at EL3 we incorrectly take
the exception to EL2, not EL3; sent a patch to fix this
- looking into an issue with FEAT_MOPS copies going backwards across
page boundaries
* QEMU-292 [ARMv8.3 FEAT_NV, Nested Virtualization]
- realised we need to do some cleanup of how we handle the FEAT_VHE register
aliases, as the way we currently do them makes the FEAT_NV register
trapping a little awkward. Wrote the necessary patches; they'll go
into the FEAT_NV patchset when it's eventually ready to send out.
-- PMM