From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: open list <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>
Cc: Arnd Bergmann <arnd@arndb.de>,
Anders Roxell <anders.roxell@linaro.org>,
Marc Zyngier <maz@kernel.org>,
joey.gouly@arm.com, Oliver Upton <oliver.upton@linux.dev>
Subject: gcc-8: arm64/kvm/pauth.: Error: unknown architectural extension `pauth'
Date: Mon, 22 Apr 2024 14:04:43 +0530 [thread overview]
Message-ID: <CA+G9fYsCL5j-9JzqNH5X03kikL=O+BaCQQ8Ao3ADQvxDuZvqcg@mail.gmail.com> (raw)
The arm64 defconfig build failed with gcc-8 and passed with gcc-13.
Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
Build log:
---
/tmp/ccSUNNZy.s: Assembler messages:
/tmp/ccSUNNZy.s:3159: Error: unknown architectural extension `pauth'
make[5]: *** [scripts/Makefile.build:244: arch/arm64/kvm/pauth.o] Error 1
Steps to reproduce:
---
# tuxmake --runtime podman --target-arch arm64 --toolchain gcc-8
--kconfig defconfig
Links:
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240422/testrun/23551634/suite/build/test/gcc-8-defconfig/details/
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240422/testrun/23551634/suite/build/test/gcc-8-defconfig/log
- https://storage.tuxsuite.com/public/linaro/lkft/builds/2fRe0ZWWmise7cetIz0aXdnq4jJ/
--
Linaro LKFT
https://lkft.linaro.org
next reply other threads:[~2024-04-22 8:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 8:34 Naresh Kamboju [this message]
2024-04-22 9:13 ` gcc-8: arm64/kvm/pauth.: Error: unknown architectural extension `pauth' Mark Rutland
2024-04-22 9:25 ` Arnd Bergmann
2024-04-22 9:40 ` Mark Rutland
2024-04-22 12:11 ` Arnd Bergmann
2024-04-22 17:20 ` Mark Rutland
2024-04-22 18:44 ` Arnd Bergmann
2024-04-22 22:58 ` Marc Zyngier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+G9fYsCL5j-9JzqNH5X03kikL=O+BaCQQ8Ao3ADQvxDuZvqcg@mail.gmail.com' \
--to=naresh.kamboju@linaro.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=joey.gouly@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=regressions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).