From: Yonghong Song <yonghong.song@linux.dev>
To: Alan Maguire <alan.maguire@oracle.com>,
Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
dwarves@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
bpf@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH dwarves] bpf_encoder: Fix a verbose output issue
Date: Wed, 14 Jan 2026 21:00:44 -0800 [thread overview]
Message-ID: <20260115050044.2220436-1-yonghong.song@linux.dev> (raw)
For the following test.c:
$ cat test.c
unsigned tar(int a);
__attribute__((noinline)) static int foo(int a, int b)
{
return tar(a) + tar(a + 1);
}
__attribute__((noinline)) int bar(int a)
{
foo(a, 1);
return 0;
}
The llvm compilation:
$ clang -O2 -g -c test.c
And then
$ pahole -JV test.o
btf_encoder__new: 'test.o' doesn't have '.data..percpu' sectio n
File test.o:
[1] INT unsigned int size=4 nr_bits=32 encoding=(none)
[2] INT int size=4 nr_bits=32 encoding=SIGNED
search cu 'test.c' for percpu global variables.
[3] FUNC_PROTO (anon) return=2 args=(2 a, [4] FUNC bar type_id=3
[5] FUNC_PROTO (anon) return=2 args=(2 a, 2 b, [6] FUNC foo type_id=5
The above confused format is due to btf_encoder__add_func_proto_for_state().
The "is_last = param_idx == nr_params" is always false since param_idx
starts from 0. The below change fixed the issue:
is_last = param_idx == (nr_params - 1)
With the fix, 'pahole -JV test.o' will produce the following:
...
[3] FUNC_PROTO (anon) return=2 args=(2 a)
[4] FUNC bar type_id=3
[5] FUNC_PROTO (anon) return=2 args=(2 a, 2 b)
[6] FUNC foo type_id=5
...
Signed-off-by: Yonghong Song <yonghong.song@linux.dev>
---
btf_encoder.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/btf_encoder.c b/btf_encoder.c
index b37ee7f..09a5cda 100644
--- a/btf_encoder.c
+++ b/btf_encoder.c
@@ -895,7 +895,7 @@ static int32_t btf_encoder__add_func_proto_for_state(struct btf_encoder *encoder
for (param_idx = 0; param_idx < nr_params; param_idx++) {
p = &state->parms[param_idx];
name = btf__name_by_offset(btf, p->name_off);
- is_last = param_idx == nr_params;
+ is_last = param_idx == (nr_params - 1);
/* adding BTF data may result in a move of the
* name string memory, so make a temporary copy.
--
2.47.3
next reply other threads:[~2026-01-15 5:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 5:00 Yonghong Song [this message]
2026-01-15 9:41 ` [PATCH dwarves] bpf_encoder: Fix a verbose output issue Alan Maguire
2026-01-15 17:09 ` Yonghong Song
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=20260115050044.2220436-1-yonghong.song@linux.dev \
--to=yonghong.song@linux.dev \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=kernel-team@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.