From: "Arnd Bergmann" <arnd@arndb.de>
To: "Naresh Kamboju" <naresh.kamboju@linaro.org>,
Netdev <netdev@vger.kernel.org>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
"open list" <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
"Linux Regressions" <regressions@lists.linux.dev>,
linux-rdma@vger.kernel.org
Cc: "Ard Biesheuvel" <ardb@kernel.org>,
"Patrisious Haddad" <phaddad@nvidia.com>,
"Michael Guralnik" <michaelgur@nvidia.com>,
"Moshe Shemesh" <moshe@nvidia.com>,
"Tariq Toukan" <tariqt@nvidia.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Dan Carpenter" <dan.carpenter@linaro.org>,
"Anders Roxell" <anders.roxell@linaro.org>,
"Benjamin Copeland" <benjamin.copeland@linaro.org>,
"Nathan Chancellor" <nathan@kernel.org>
Subject: Re: next-20251002: arm64: gcc-8-defconfig: Assembler messages: Error: unknown architectural extension `simd;'
Date: Mon, 06 Oct 2025 13:58:41 +0200 [thread overview]
Message-ID: <a2357b92-8a8a-4d79-afb8-0bb8aee244ac@app.fastmail.com> (raw)
In-Reply-To: <CA+G9fYt+9QZ4TwEx7+m2S5Vtn7cq1N54oGceSR72upZJTrzkng@mail.gmail.com>
On Mon, Oct 6, 2025, at 13:31, Naresh Kamboju wrote:
> + linux-rdma@vger.kernel.org
>
> On Mon, 6 Oct 2025 at 17:00, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
>> ### Build error log
>> /tmp/cclfMnj9.s: Assembler messages:
>> /tmp/cclfMnj9.s:656: Error: unknown architectural extension `simd;'
>> make[8]: *** [scripts/Makefile.build:287:
>> drivers/net/ethernet/mellanox/mlx5/core/wc.o] Error 1
>>
>> Suspecting commit,
>> $ git blame -L 269 drivers/net/ethernet/mellanox/mlx5/core/wc.c
>> fd8c8216648cd8 (Patrisious Haddad 2025-09-29 00:08:08 +0300 269)
>> (".arch_extension simd;\n\t"
>> fd8c8216648cd net/mlx5: Improve write-combining test reliability for
>> ARM64 Grace CPUs
>>
>> ## Source
>> * Kernel version: 6.17.0
>> * Git tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next.git
>> * Git commit: 47a8d4b89844f5974f634b4189a39d5ccbacd81c
>> * Architectures: arm64
>> * Toolchains: gcc-8
>> * Kconfigs: defconfig
>>
Nathan already analyzed the problem and suggested a fix, but I could
not find a patch on the mailing list so far and sent his suggestion
now. Please check
https://lore.kernel.org/all/20251006115640.497169-1-arnd@kernel.org/
Arnd
prev parent reply other threads:[~2025-10-06 11:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 11:30 Naresh Kamboju
2025-10-06 11:31 ` Naresh Kamboju
2025-10-06 11:58 ` Arnd Bergmann [this message]
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=a2357b92-8a8a-4d79-afb8-0bb8aee244ac@app.fastmail.com \
--to=arnd@arndb.de \
--cc=anders.roxell@linaro.org \
--cc=ardb@kernel.org \
--cc=benjamin.copeland@linaro.org \
--cc=dan.carpenter@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=michaelgur@nvidia.com \
--cc=moshe@nvidia.com \
--cc=naresh.kamboju@linaro.org \
--cc=nathan@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=phaddad@nvidia.com \
--cc=regressions@lists.linux.dev \
--cc=tariqt@nvidia.com \
/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
all inboxes | Powered by JetHome®