Hi,
I guess this is a false alarm since the error message was
FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2b (internal compiler
error: in core_vals, at cp/module.cc:6110)
and is now:
FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2b (internal compiler
error: in core_vals, at cp/module.cc:6112)
(that is, only the line number changes)
Thanks,
Christophe
On Thu, 11 Jan 2024 at 08:32, <ci_notify(a)linaro.org> wrote:
>
> Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> We track this report status in https://linaro.atlassian.net/browse/GNU-1101 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In master-aarch64 after:
>
> | commit gcc-14-7074-gf9fbf93dc82
> | Author: waffl3x <waffl3x(a)protonmail.com>
> | Date: Sun Jan 7 00:00:10 2024 +0000
> |
> | c++: P0847R7 (deducing this) - prerequisite changes. [PR102609]
> |
> | Adds the xobj_flag member to lang_decl_fn and a corresponding member access
> | macro and predicate to support the addition of explicit object member
> | functions. Additionally, since explicit object member functions are also
> | non-static member functions, we need to change uses of
> | DECL_NONSTATIC_MEMBER_FUNCTION_P to clarify whether they intend to include
> | ... 76 lines of the commit log omitted.
>
> FAIL: 15 regressions: 15 progressions
>
> regressions.sum:
> === g++ tests ===
>
> Running g++:g++.dg/modules/modules.exp ...
> FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6112)
> FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2a (internal compiler error: in core_vals, at cp/module.cc:6112)
> FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6112)
> FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6112)
> FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2a (internal compiler error: in core_vals, at cp/module.cc:6112)
> FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6112)
> FAIL: g++.dg/modules/xtreme-header-5_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6112)
> ... and 10 more entries
>
> progressions.sum:
> === g++ tests ===
>
> Running g++:g++.dg/modules/modules.exp ...
> FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6110)
> FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++2a (internal compiler error: in core_vals, at cp/module.cc:6110)
> FAIL: g++.dg/modules/xtreme-header-1_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6110)
> FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++17 (internal compiler error: in core_vals, at cp/module.cc:6110)
> FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2a (internal compiler error: in core_vals, at cp/module.cc:6110)
> FAIL: g++.dg/modules/xtreme-header-2_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6110)
> FAIL: g++.dg/modules/xtreme-header-5_a.H -std=c++2b (internal compiler error: in core_vals, at cp/module.cc:6110)
> ... and 10 more entries
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/8… .
> The full lists of regressions and progressions are in
> - https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/8… .
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/8… .
>
> The configuration of this build is:
> CI config tcwg_gnu_native_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_native_check_gcc--master-aarch64-build/8…
> Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/8…
>
> 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/f9fbf93dc82525a0f54a2293b7ec92d657…
>
> List of configurations that regressed due to this commit :
> * tcwg_gnu_native_check_gcc
> ** master-aarch64
> *** FAIL: 15 regressions: 15 progressions
> *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
> *** https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/8…
At 08:36 +0000 on Friday, 2024-01-12, wrote ci_notify(a)linaro.org:
> 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.
Ok, I will fix this error as soon as possible!
Hi David,
As you have probably guessed, this is a false alarm: the testcases you
updated were already failing before your patch, but it changed the
line numbers, thus making the scripts think a failure disappeared and
a new one appeared.
Thanks,
Christophe
On Mon, 8 Jan 2024 at 01:15, <ci_notify(a)linaro.org> wrote:
>
> Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> We track this report status in https://linaro.atlassian.net/browse/GNU-1094 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In bootstrap_check master-arm-check_bootstrap_lto after:
>
> | commit gcc-14-6840-g86f535cb466
> | Author: David Edelsohn <dje.gcc(a)gmail.com>
> | Date: Tue Dec 26 16:44:09 2023 +0000
> |
> | testsuite: Skip analyzer out-of-bounds-diagram on AIX.
> |
> | The out-of-bounds diagram tests fail on AIX.
> |
> | gcc/testsuite/ChangeLog:
> | * gcc.dg/analyzer/out-of-bounds-diagram-17.c: Skip on AIX.
> | * gcc.dg/analyzer/out-of-bounds-diagram-18.c: Same.
> | ... 2 lines of the commit log omitted.
>
> FAIL: 2 regressions: 2 progressions
>
> regressions.sum:
> === gcc tests ===
>
> Running gcc:gcc.dg/analyzer/analyzer.exp ...
> FAIL: gcc.dg/analyzer/out-of-bounds-diagram-17.c expected multiline pattern lines 15-36
> FAIL: gcc.dg/analyzer/out-of-bounds-diagram-18.c expected multiline pattern lines 15-44
>
> === Results Summary ===
>
> progressions.sum:
> === gcc tests ===
>
> Running gcc:gcc.dg/analyzer/analyzer.exp ...
> FAIL: gcc.dg/analyzer/out-of-bounds-diagram-17.c expected multiline pattern lines 14-35
> FAIL: gcc.dg/analyzer/out-of-bounds-diagram-18.c expected multiline pattern lines 14-43
>
> === Results Summary ===
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_bootstrap_check--master-arm-check_bootstrap_… .
> The full lists of regressions and progressions are in
> - https://ci.linaro.org/job/tcwg_bootstrap_check--master-arm-check_bootstrap_… .
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_bootstrap_check--master-arm-check_bootstrap_… .
>
> The configuration of this build is:
> CI config tcwg_bootstrap_check master-arm-check_bootstrap_lto
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_bootstrap_check--master-arm-check_bootstrap_…
> Reference build : https://ci.linaro.org/job/tcwg_bootstrap_check--master-arm-check_bootstrap_…
>
> 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/86f535cb4664fcaf96ff12942887db949b…
>
> List of configurations that regressed due to this commit :
> * tcwg_bootstrap_check
> ** master-arm-check_bootstrap_lto
> *** FAIL: 2 regressions: 2 progressions
> *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
> *** https://ci.linaro.org/job/tcwg_bootstrap_check--master-arm-check_bootstrap_…
Progress (short week, 2 days):
* UM-2 [QEMU upstream maintainership]
- post holiday email/slack/etc catchup
- started merging pullrequests (I'm doing release management for
the 9.0 cycle)
- investigated a reported regression in virtio-pci running Linux
on 32-bit arm emulation. This turns out to be that we made a change
that *fixed* a bug in QEMU (we were incorrectly laying out the 'virt'
board assuming a 32-bit v8 CPU couldn't use LPAE), which reveals
a bug in Linux (it mishandles the PCI controller DTB entry saying
the ECAM region is above the 4GB boundary)...
* QEMU-623 [Nested Virtualization Emulation]
- dealt with the minor review followups on this patchset; just waiting
for one last reviewed-by tag before we can upstream it
-- PMM
> -----Original Message-----
> From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
> Sent: Friday, December 29, 2023 7:40 AM
> To: Andrew Pinski (QUIC) <quic_apinski(a)quicinc.com>
> Cc: gcc-regression(a)gcc.gnu.org
> Subject: [Linaro-TCWG-CI] gcc-14-6861-g200531d5b9f: FAIL: 1 regressions
> on arm
>
> Dear contributor, our automatic CI has detected problems related to your
> patch(es). Please find some details below. If you have any questions, please
> follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg
> channel, or ping your favourite Linaro toolchain developer on the usual project
> channel.
>
> We appreciate that it might be difficult to find the necessary logs or reproduce
> the issue locally. If you can't get what you need from our CI within minutes, let
> us know and we will be happy to help.
>
> We track this report status in https://linaro.atlassian.net/browse/GNU-1091 ,
> please let us know if you are looking at the problem and/or when you have a
> fix.
First I suspect this was failing before r14-6822-g01f4251b8775c8 and I just return it back to that state.
The big ask I have is for reports like this, to include the exact gcc configure line that was used.
In this case, is GCC configured to include neon by default? If so then the testcase needs to be updated to add an option to disable neon.
If not, then someone else will need to look into why the testcase is failing.
Basically, the update I did was disable vectorization on a loop which was not being vectorized before r14-6822-g01f4251b8775c8.
Thanks,
Andrew Pinski
>
> In master-arm after:
>
> | commit gcc-14-6861-g200531d5b9f
> | Author: Andrew Pinski <quic_apinski(a)quicinc.com>
> | Date: Thu Dec 28 20:26:01 2023 -0800
> |
> | Fix gen-vect-26.c testcase after loops with multiple exits [PR113167]
> |
> | This fixes the gcc.dg/tree-ssa/gen-vect-26.c testcase by adding
> | `#pragma GCC novector` in front of the loop that is doing the checking
> | of the result. We only want to test the first loop to see if it can be
> | vectorize.
> |
> | ... 9 lines of the commit log omitted.
>
> FAIL: 1 regressions
>
> regressions.sum:
> === gcc tests ===
>
> Running gcc:gcc.dg/tree-ssa/tree-ssa.exp ...
> FAIL: gcc.dg/tree-ssa/gen-vect-26.c scan-tree-dump-times vect "Alignment of
> access forced using peeling" 1
>
> === Results Summary ===
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-
> build/1147/artifact/artifacts/00-sumfiles/ .
> The full lists of regressions and progressions are in
> - https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-
> build/1147/artifact/artifacts/notify/ .
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-
> build/1147/artifact/artifacts/sumfiles/xfails.xfail .
>
> The configuration of this build is:
> CI config tcwg_gnu_cross_check_gcc master-arm
>
> -----------------8<--------------------------8<--------------------------8<----------------
> ----------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-
> arm-build/1147/artifact/artifacts
> Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--
> master-arm-build/1146/artifact/artifacts
>
> Reproduce last good and first bad builds: https://git-
> us.linaro.org/toolchain/ci/interesting-
> commits.git/plain/gcc/sha1/200531d5b9fb99eca2b0d6b8d1e42d17641322
> 5f/tcwg_gnu_cross_check_gcc/master-arm/reproduction_instructions.txt
>
> Full commit : https://github.com/gcc-
> mirror/gcc/commit/200531d5b9fb99eca2b0d6b8d1e42d176413225f
>
> List of configurations that regressed due to this commit :
> * tcwg_gnu_cross_check_gcc
> ** master-arm
> *** FAIL: 1 regressions
> *** https://git-us.linaro.org/toolchain/ci/interesting-
> commits.git/plain/gcc/sha1/200531d5b9fb99eca2b0d6b8d1e42d17641322
> 5f/tcwg_gnu_cross_check_gcc/master-arm/details.txt
> *** https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-
> build/1147/artifact/artifacts
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