From: Vineet Gupta <vineet.gupta@linux.dev>
To: sashiko-reviews@lists.linux.dev
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next 3/3] selftests/bpf: Enable some of the blocked cpuv4 instruction tests for bpf-gcc
Date: Fri, 21 Aug 2026 16:38:05 -0700 [thread overview]
Message-ID: <26177133-4030-4e0b-ae68-0d892cf9ad5b@linux.dev> (raw)
In-Reply-To: <20260821201922.53F641F000E9@smtp.kernel.org>
On 8/21/26 1:19 PM, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] The newly added multi-line comment for the gas bug workaround does not follow the required BPF subsystem comment style.
> --
>
> --- Patch [3]: [PATCH bpf-next 3/3] selftests/bpf: Enable some of the blocked cpuv4 instruction tests for bpf-gcc ---
> commit 55694625f0a27b85eb77860cd1b4f07749dec04c
> Author: Vineet Gupta <vineet.gupta@linux.dev>
>
> selftests/bpf: Enable some of the blocked cpuv4 instruction tests for bpf-gcc
>
> This commit enables several blocked BPF CPUv4 instruction tests for bpf-gcc
> by checking specific feature macros instead of relying solely on clang checks.
> It also skips address space cast tests for bpf-gcc as the feature is not
> currently supported, while retaining the existing tests for clang.
>
>> diff --git a/tools/testing/selftests/bpf/progs/compute_live_registers.c b/tools/testing/selftests/bpf/progs/compute_live_registers.c
>> index 338e67cd8856a..c7d5a0abff2c3 100644
>> --- a/tools/testing/selftests/bpf/progs/compute_live_registers.c
>> +++ b/tools/testing/selftests/bpf/progs/compute_live_registers.c
>> @@ -299,7 +299,14 @@ __naked void gotol(void)
>> "r3 = 24;"
>> "if r1 > 0x7 goto +2;"
>> "r0 = r2;"
>> +#ifdef __clang__
>> "gotol +1;"
>> +#else
>> + /* gas mis-parses 'gotol +1' as 'goto l+1', same encoding
>> + * without the sign (binutils PR gas/34558).
>> + */
> [Severity: Low]
> This isn't a bug, but does this multi-line comment follow the preferred BPF
> subsystem comment style?
>
> The BPF subsystem requires the opening /* to be on its own line:
>
> /*
> * gas mis-parses 'gotol +1' as 'goto l+1', same encoding
> * without the sign (binutils PR gas/34558).
> */
Right, I'll fix this in v2.
Thx,
-Vineet
next prev parent reply other threads:[~2026-08-21 23:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 20:13 [PATCH bpf-next 0/3] selftests/bpf: unblock bpf-gcc test coverage Vineet Gupta
2026-08-21 20:13 ` [PATCH bpf-next 1/3] selftests/bpf: name the remaining placeholder programs dummy_test [NFC] Vineet Gupta
2026-08-24 18:46 ` Eduard Zingerman
2026-08-21 20:13 ` [PATCH bpf-next 2/3] selftests/bpf: report placeholder tests as SKIP, not OK Vineet Gupta
2026-08-21 21:00 ` bot+bpf-ci
2026-08-21 23:48 ` Vineet Gupta
2026-08-24 18:53 ` Eduard Zingerman
2026-08-21 20:13 ` [PATCH bpf-next 3/3] selftests/bpf: Enable some of the blocked cpuv4 instruction tests for bpf-gcc Vineet Gupta
2026-08-21 20:19 ` sashiko-bot
2026-08-21 23:38 ` Vineet Gupta [this message]
2026-08-24 19:04 ` Eduard Zingerman
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=26177133-4030-4e0b-ae68-0d892cf9ad5b@linux.dev \
--to=vineet.gupta@linux.dev \
--cc=bpf@vger.kernel.org \
--cc=sashiko-reviews@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