From: Florian Westphal <fw@strlen.de>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: net-next 32-bit clang build error in net/netfilter/nf_synproxy_core.o
Date: Mon, 1 Jun 2026 21:14:08 +0200 [thread overview]
Message-ID: <ah3aAO7oFuh7xei5@strlen.de> (raw)
In-Reply-To: <a28df759-d0e9-41c0-97c7-5f89a18d54e2@oss.qualcomm.com>
Jeff Johnson <jeff.johnson@oss.qualcomm.com> wrote:
> wireless-next/main has fast-forwarded to e7d6bd24e883 and I'm in the process
> of also fast-forwarding ath/ath-next, but I'm seeing a build failure:
>
> In file included from ../net/netfilter/nf_synproxy_core.c:7:
> In file included from ../include/linux/skbuff.h:26:
> In file included from ../include/net/checksum.h:21:
> In file included from ../arch/x86/include/asm/checksum.h:9:
> ../arch/x86/include/asm/checksum_32.h:149:6: error: inline assembly requires more registers than available
> 149 | asm("addl 0(%1), %0 ;\n"
> | ^
> 1 error generated.
> make[5]: *** [../scripts/Makefile.build:289: net/netfilter/nf_synproxy_core.o] Error 1
>
> This is with "ARCH=i386 LLVM=llvm-19.1.7-x86_64/bin/"
>
> I use a config made via: make $allmodconfig
>
> A lore search doesn't show any recent instances of this issue.
>
> Rebuilding from scratch shows the same issue.
>
> Any thoughts?
Happens since 403cec8ab6d0 ("netfilter: add option for GCOV
profiling"). 'allmodconfig' sets CONFIG_GCOV_PROFILE_NETFILTER=y
Same problem after revert or plain 7.0 when I set CONFIG_GCOV_PROFILE_ALL=y
(which depends on !COMPILE_TEST so its off for 'make allmodconfig').
prev parent reply other threads:[~2026-06-01 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 12:37 [GIT PULL] wireless-next-2026-05-28 Johannes Berg
2026-05-29 0:12 ` patchwork-bot+netdevbpf
2026-06-01 16:43 ` net-next 32-bit clang build error in net/netfilter/nf_synproxy_core.o Jeff Johnson
2026-06-01 19:14 ` Florian Westphal [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=ah3aAO7oFuh7xei5@strlen.de \
--to=fw@strlen.de \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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