ci_notify@linaro.org writes:

In CI config tcwg_kernel/gnu-master-arm-next-allyesconfig after:

| commit v6.9-rc2-36-gfc4216add64ee | Author: Samuel Holland samuel.holland@sifive.com | Date: Fri Mar 29 00:18:28 2024 -0700 | | drm/amd/display: use ARCH_HAS_KERNEL_FPU_SUPPORT | | Now that all previously-supported architectures select | ARCH_HAS_KERNEL_FPU_SUPPORT, this code can depend on that symbol instead | of the existing list of architectures. It can also take advantage of the | common kernel-mode FPU API and method of adjusting CFLAGS. | | ... 21 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: 22511

From # reset_artifacts: -10 # build_abe binutils: -9 # build_abe stage1: -5 # build_abe qemu: -2 # linux_n_obj: 22321 # linux build successful: all

This problem still reproduces on next-20240410, so I reported it to the patch author. He responded here:

https://lore.kernel.org/linux-arm-kernel/75a37a4b-f516-40a3-b6b5-4aa1636f9b6...

mentioning that it's a shortcoming of GCC on arm:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91970

Though Andrew Pinski has just disagreed with that assessment.

-- Thiago