[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87zgh2y35y.wl-maz@kernel.org>
Date: Thu, 21 Jul 2022 15:02:33 +0100
From: Marc Zyngier <maz@...nel.org>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: Linux-Next Mailing List <linux-next@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
regressions@...ts.linux.dev, lkft-triage@...ts.linaro.org,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Catalin Marinas <catalin.marinas@....com>,
Mark Rutland <mark.rutland@....com>,
Mark Brown <broonie@...nel.org>, Arnd Bergmann <arnd@...db.de>,
Aishwarya TCV <Aishwarya.TCV@....com>,
Ard Biesheuvel <ardb@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: arm64: defconfig build failed on Linux next-20220721
On Thu, 21 Jul 2022 14:53:03 +0100,
Naresh Kamboju <naresh.kamboju@...aro.org> wrote:
>
> arm64 defconfig build failed on Linux next-20220721 tag kernel.
>
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
>
> Regressions found on arm64:
> - build-gcc-11-lkftconfig-64k_page_size
> - build-gcc-11-lkftconfig-rcutorture
> - build-gcc-11-lkftconfig-devicetree
> - build-gcc-11-lkftconfig
> - build-gcc-11-lkftconfig-debug
> - build-gcc-11-lkftconfig-armv8_features
> - build-gcc-11-lkftconfig-kselftest
> - build-gcc-11-lkftconfig-kunit
> - build-gcc-11-lkftconfig-libgpiod
> - build-gcc-11-lkftconfig-kasan
> - build-clang-12-lkftconfig
> - build-clang-14-lkftconfig
> - build-clang-13-lkftconfig
> - build-clang-nightly-lkftconfig
> - build-gcc-11-lkftconfig-debug-kmemleak
>
> make --silent --keep-going --jobs=8
> O=/home/tuxbuild/.cache/tuxmake/builds/1/build
> CROSS_COMPILE_COMPAT=arm-linux-gnueabihf- ARCH=arm64
> CROSS_COMPILE=aarch64-linux-gnu- 'CC=sccache aarch64-linux-gnu-gcc'
> 'HOSTCC=sccache gcc'
> /builds/linux/arch/arm64/kernel/head.S: Assembler messages:
> /builds/linux/arch/arm64/kernel/head.S:334: Error: immediate cannot be
> moved by a single instruction
See https://lore.kernel.org/r/20220721124244.903567-1-maz@kernel.org
as a potential workaround.
Another solution would be to have Peter's patch in 5.19 but not in
5.20.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists