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
On Wed, 8 Nov 2023, ci_notify--- via Gcc-regression 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-arm after:
>
> | commit gcc-14-5237-gf27246b0096
> | Author: Joseph Myers <joseph(a)codesourcery.com>
> | Date: Wed Nov 8 00:15:22 2023 +0000
> |
> | testsuite: Rename c2x-*, gnu2x-* tests to c23-*, gnu23-*
> |
> | Completing the move to refer to C23 in place of C2X, rename all tests
> | with "c2x" or "gnu2x" in their names to use "c23" or "gnu23" instead.
> | 17 files in the testsuite that referred to such tests (or, in one
> | case, a generated .i file to be scanned) by those names are updated
> | for the renaming.
> | ... 467 lines of the commit log omitted.
>
> FAIL: 8 regressions: 8 progressions
>
> regressions.sum:
> === gcc tests ===
>
> Running gcc:gcc.dg/dg.exp ...
> FAIL: gcc.dg/c23-stdarg-4.c execution test
>
> Running gcc:gcc.dg/torture/dg-torture.exp ...
> FAIL: gcc.dg/torture/c23-stdarg-split-1a.c -O0 execution test
> FAIL: gcc.dg/torture/c23-stdarg-split-1a.c -O1 execution test
> FAIL: gcc.dg/torture/c23-stdarg-split-1a.c -O2 execution test
> FAIL: gcc.dg/torture/c23-stdarg-split-1a.c -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test
> ... and 5 more entries
This is clearly just a renaming of tests that were already failing. I'd
certainly encourage the relevant target maintainers to investigate and fix
the failing tests (which probably indicate a back-end change is needed to
make variable argument access work correctly in a function with no named
arguments - some architectures were fixed by the change in bug 107453, but
it wouldn't be surprising if other architectures need back-end changes).
--
Joseph S. Myers
joseph(a)codesourcery.com
It also caused x86 backend regression. Please help verify it.
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: Saturday, November 4, 2023 2:43 PM
> To: uecker(a)tugraz.at
> Cc: ci_notify(a)linaro.org; gcc-regression(a)gcc.gnu.org
> Subject: [Linaro-TCWG-CI] gcc-14-5115-g6e9ee44d96e: 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-5115-g6e9ee44d96e
> | Author: Martin Uecker <uecker(a)tugraz.at>
> | Date: Thu Apr 13 19:35:15 2023 +0200
> |
> | Reduce false positives for -Wnonnull for VLA parameters [PR98541]
> |
> | This patch limits the warning about NULL arguments to VLA
> | parameters declared [static n].
> |
> | PR c/98541
> |
> | ... 8 lines of the commit log omitted.
>
> FAIL: 1 regressions
>
> regressions.sum:
> === gcc tests ===
>
> Running gcc:gcc.dg/dg.exp ...
> FAIL: gcc.dg/Wnonnull-4.c (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-arm-
> build/1213/artifact/artifacts/00-sumfiles/ .
> The full lists of regressions and progressions are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-
> build/1213/artifact/artifacts/notify/ .
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-
> build/1213/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/1213/artifact/artifacts
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-
> build/1212/artifact/artifacts
>
> Reproduce last good and first bad builds: https://git-
> us.linaro.org/toolchain/ci/interesting-
> commits.git/plain/gcc/sha1/6e9ee44d96e5bda8808dd9d8ccf58d2525383f6
> b/tcwg_gcc_check/master-arm/reproduction_instructions.txt
>
> Full commit : https://github.com/gcc-
> mirror/gcc/commit/6e9ee44d96e5bda8808dd9d8ccf58d2525383f6b
>
> Latest bug report status : https://linaro.atlassian.net/browse/GNU-993
>
> 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/6e9ee44d96e5bda8808dd9d8ccf58d2525383f6
> b/tcwg_gcc_check/master-arm/details.txt
> *** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1213/
Hello,
# TCWG CI
- Working on Abe change to always add detected flaky tests to the
flaky.xfail file, even if they are already present in the baseline
results. Sent a few versions of Gerrit review request already.
# [GNU-981] FEAT_GCS (Guarded Control Stack) support in GDB
- Prepared environment to develop and test GDB: built Linux kernel from
Mark Brown's arm64-gcs branch and booted it in an Arm FVP supporting
the feature. Successfully ran native GDB in it to debug a program
(though I didn't use any GCS feature for this test).
--
Thiago
Progress:
* UM-2 [QEMU upstream maintainership]
- investigated and fixed a few bugs in FEAT_MOPS; patches sent
- reviewed patch fixing bug in virt ACPI table for debug UART; added
the necessary update-the-reference-files patches for 'make check'.
Debugged why it broke console output on Linux -- turns out that Linux
has a bug where acpi_parse_spcr() and pl011_console_match() disagree
about how the former should tell the latter "use 16-bit MMIO"...
We'll work around this by having the ACPI table report 32-bit MMIO;
Raspberry Pi 4 firmware on real hardware already does that, so it
should be a safe choice.
- sent patch fixing failure to report BTI GP state correctly when
doing a two-stage page table walk
- code review and assembly of a pull request (softfreeze next week...)
* QEMU-292 [ARMv8.3 FEAT_NV, Nested Virtualization]
- got to a (hopefully) code-complete but untested state; will probably
put this to one side for the moment leading up to softfreeze
- tracked down the kernel and kvmtool patchsets that will be needed
to test this (they are not upstream yet)
thanks
-- 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.
In CI config tcwg_kernel/gnu-master-aarch64-mainline-allyesconfig after:
| commit gcc-14-5059-gd880e093d92
| Author: Martin Uecker <uecker(a)tugraz.at>
| Date: Thu Jul 27 13:36:05 2023 +0200
|
| c: Add Walloc-size to warn about insufficient size in allocations [PR71219]
|
| Add option Walloc-size that warns about allocations that have
| insufficient storage for the target type of the pointer the
| storage is assigned to. Added to Wextra.
|
| PR c/71219
| ... 14 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:
22669
# First few build errors in logs:
# 00:33:49 drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v8.c:241:15: error: allocation of insufficient size ‘4’ for type ‘uint32_t[2]’ {aka ‘unsigned int[2]’} with size ‘8’ [-Werror=alloc-size]
# 00:33:49 drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v8.c:327:15: error: allocation of insufficient size ‘4’ for type ‘uint32_t[2]’ {aka ‘unsigned int[2]’} with size ‘8’ [-Werror=alloc-size]
# 00:33:49 drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v9.c:368:15: error: allocation of insufficient size ‘4’ for type ‘uint32_t[2]’ {aka ‘unsigned int[2]’} with size ‘8’ [-Werror=alloc-size]
# 00:33:49 drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v9.c:465:15: error: allocation of insufficient size ‘4’ for type ‘uint32_t[2]’ {aka ‘unsigned int[2]’} with size ‘8’ [-Werror=alloc-size]
# 00:33:50 make[6]: *** [scripts/Makefile.build:243: drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v8.o] Error 1
# 00:33:52 drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_arcturus.c:203:15: error: allocation of insufficient size ‘4’ for type ‘uint32_t[2]’ {aka ‘unsigned int[2]’} with size ‘8’ [-Werror=alloc-size]
# 00:33:53 make[6]: *** [scripts/Makefile.build:243: drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_arcturus.o] Error 1
# 00:33:53 make[6]: *** [scripts/Makefile.build:243: drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v9.o] Error 1
# 00:33:56 drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gc_9_4_3.c:144:15: error: allocation of insufficient size ‘4’ for type ‘uint32_t[2]’ {aka ‘unsigned int[2]’} with size ‘8’ [-Werror=alloc-size]
# 00:33:57 make[6]: *** [scripts/Makefile.build:243: drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gc_9_4_3.o] Error 1
From
# reset_artifacts:
-10
# build_abe binutils:
-9
# build_abe stage1:
-5
# build_abe qemu:
-2
# linux_n_obj:
22751
# linux build successful:
all
The configuration of this build is:
CI config tcwg_kernel/gnu-master-aarch64-mainline-allyesconfig
-----------------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-mainline-allyesco…
Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-mainline-allyesco…
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/d880e093d92084f55b10626610ef059fd9…
Latest bug report status : https://linaro.atlassian.net/browse/GNU-990
List of configurations that regressed due to this commit :
* tcwg_kernel
** gnu-master-aarch64-mainline-allyesconfig
*** Failure
*** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
*** https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-mainline-allyesco…
On Wed, Nov 1, 2023 at 7:42 AM <ci_notify(a)linaro.org> wrote:
>
> Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> In CI config tcwg_kernel/llvm-master-arm-mainline-allmodconfig after:
ok, so ARCH=arm allmodconfig on mainline...
>
> | commit v6.6-rc1-17-g1c6fdbd8f246
> | Author: Kent Overstreet <kent.overstreet(a)gmail.com>
> | Date: Thu Mar 16 22:18:50 2017 -0800
> |
> | bcachefs: Initial commit
> |
> | Initially forked from drivers/md/bcache, bcachefs is a new copy-on-write
> | filesystem with every feature you could possibly want.
> |
> | Website: https://bcachefs.org
> |
> | ... 1 lines of the commit log omitted.
>
> Results changed to
> # reset_artifacts:
> -10
> # build_abe binutils:
> -9
> # build_kernel_llvm:
> -5
> # build_abe qemu:
> -2
> # linux_n_obj:
> 23730
> # First few build errors in logs:
>
> # 00:23:16 fs/bcachefs/btree_cache.h:45:43: error: array index 0 is past the end of the array (that has type 'const __u64[0]' (aka 'const unsigned long long[0]')) [-Werror,-Warray-bounds]
> # 00:23:17 fs/bcachefs/alloc.c:332:9: error: call to undeclared function 'COUNT_ARGS'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
^
$ file fs/bcachefs/alloc.c
fs/bcachefs/alloc.c: cannot open `fs/bcachefs/alloc.c' (No such file
or directory)
> # 00:23:17 make[4]: *** [scripts/Makefile.build:243: fs/bcachefs/alloc.o] Error 1
> # 00:23:29 fs/bcachefs/btree_cache.h:45:43: error: array index 0 is past the end of the array (that has type 'const __u64[0]' (aka 'const unsigned long long[0]')) [-Werror,-Warray-bounds]
> # 00:23:30 make[4]: *** [scripts/Makefile.build:243: fs/bcachefs/bset.o] Error 1
^
$ make LLVM=1 ARCH=arm allmodconfig fs/bcachefs/bset.o
CC [M] fs/bcachefs/bset.o
$
> # 00:23:33 fs/bcachefs/btree_cache.h:45:43: error: array index 0 is past the end of the array (that has type 'const __u64[0]' (aka 'const unsigned long long[0]')) [-Werror,-Warray-bounds]
> # 00:23:33 fs/bcachefs/btree_cache.h:45:43: error: array index 0 is past the end of the array (that has type 'const __u64[0]' (aka 'const unsigned long long[0]')) [-Werror,-Warray-bounds]
> # 00:23:33 fs/bcachefs/btree_cache.c:67:9: error: array index 0 is past the end of the array (that has type 'const __u64[0]' (aka 'const unsigned long long[0]')) [-Werror,-Warray-bounds]
> # 00:23:33 fs/bcachefs/btree_cache.c:120:2: error: array index 0 is past the end of the array (that has type '__u64[0]' (aka 'unsigned long long[0]')) [-Werror,-Warray-bounds]
> # 00:23:33 fs/bcachefs/btree_cache.c:201:6: error: array index 0 is past the end of the array (that has type 'const __u64[0]' (aka 'const unsigned long long[0]')) [-Werror,-Warray-bounds]
$ make LLVM=1 ARCH=arm allmodconfig fs/bcachefs/btree_cache.o
CC [M] fs/bcachefs/btree_cache.o
$
... what's up with this report?
>
> From
> # reset_artifacts:
> -10
> # build_abe binutils:
> -9
> # build_kernel_llvm:
> -5
> # build_abe qemu:
> -2
> # linux_n_obj:
> 32815
> # linux build successful:
> all
> # linux boot successful:
> boot
>
> The configuration of this build is:
> CI config tcwg_kernel/llvm-master-arm-mainline-allmodconfig
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-arm-mainline-allmodconfi…
> Reference build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-arm-mainline-allmodconfi…
>
> Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/linux/…
>
> Full commit : https://git.linaro.org/kernel-org/linux.git/commit/?id=1c6fdbd8f2465ddfb73a…
>
> Latest bug report status : https://linaro.atlassian.net/browse/LLVM-1015
>
> List of configurations that regressed due to this commit :
> * tcwg_kernel
> ** llvm-master-arm-mainline-allmodconfig
> *** Failure
> *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/linux/…
> *** https://ci.linaro.org/job/tcwg_kernel--llvm-master-arm-mainline-allmodconfi…
--
Thanks,
~Nick Desaulniers
Progress:
* QEMU-610 [Remove qemu_get_cpu() from hardware models]
- Big rework of Cortex-A MPCore models. A common class is now used
and various duplicated code from ARM boards got removed.
Possible follow-up with QEMU-601 [Implement TYPE_CORTEXR52_PRIV].
Hello,
# [GNU-981] FEAT_GCS (Guarded Control Stack) support in GDB
- Started working on this feature. Currently adding ptrace and core file
support for the NT_ARM_GCS regset.
# Upstream community
- Implemented fix for ‘--with-auto-load-dir’ and
‘--with-auto-load-safe-path’ configure options on Windows (since Eli
mentioned it earlier this month) and posted “[PATCH] gdb/configure.ac:
Fix auto-load options to work with Windows path separator”.
--
Thiago