Dwarves debugging tools
 help / color / mirror / Atom feed
From: Eduard Zingerman <eddyz87@gmail.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Alan Maguire <alan.maguire@oracle.com>,
	 Arnaldo Carvalho de Melo <acme@kernel.org>,
	 Andrii Nakryiko <andrii@kernel.org>,
	 Ihor Solodrai <ihor.solodrai@linux.dev>,
	 bpf <bpf@vger.kernel.org>,
	dwarves@vger.kernel.org,
	 Kumar Kartikeya Dwivedi <memxor@gmail.com>
Subject: Re: pahole and gcc-14 issues
Date: Fri, 25 Apr 2025 13:25:08 -0700	[thread overview]
Message-ID: <m2r01gf0pn.fsf@gmail.com> (raw)
In-Reply-To: <CAADnVQJQuAkmE_D_ATp-hZeTtUK4Tn=BOOOx+wPtUB1QpzeQuA@mail.gmail.com> (Alexei Starovoitov's message of "Fri, 25 Apr 2025 13:16:10 -0700")

Alexei Starovoitov <alexei.starovoitov@gmail.com> writes:

[...]

>> $ diff -pruN ~/tmp/task_struct.ko.c ~/tmp/task_struct.vmlinux.c
>> --- /home/ezingerman/tmp/task_struct.ko.c       2025-04-25 12:37:48.312480603 -0700
>> +++ /home/ezingerman/tmp/task_struct.vmlinux.c  2025-04-25 12:38:03.096644654 -0700
>> @@ -18,7 +18,6 @@ struct task_struct {
>>         int static_prio;
>>         int normal_prio;
>>         unsigned int rt_priority;
>> -       long: 0;
>>         struct sched_entity se;
>
> I reproed this issue with default .ko build that includes:
> --btf_features=distilled_base
>
> Once I disabled it and did
> bpftool btf dump file ./bpf_testmod.ko --base-btf .../vmlinux format c
> the task_struct from vmlinux.h and from testmod.h became exactly the same.
> So it sounds like the 3rd issue :)
> bpftool dump of distilled btf needs work.

Mystery upon mystery.
Here is a continuation of the last one.
This is raw BTF for .ko:

  [509] STRUCT 'task_struct' size=10496 vlen=268
          ...
          'rt_priority' type_id=3 bits_offset=960
          ...

And this is raw BTF for vmlinux:

  [1] INT 'long unsigned int' size=8 bits_offset=0 nr_bits=64 encoding=(none)
  [2] CONST '(anon)' type_id=1
  [3] VOLATILE '(anon)' type_id=2
  ...
  [9] INT 'unsigned int' size=4 bits_offset=0 nr_bits=32 encoding=(none)
  ...
  [111] STRUCT 'task_struct' size=10496 vlen=268
          ...
          'rt_priority' type_id=9 bits_offset=960
          ...

Note type conflict 'volatile const long' vs 'unsigned int'.
Either something is very broken or I completely messed up the build.

  reply	other threads:[~2025-04-25 20:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-25 14:50 pahole and gcc-14 issues Alexei Starovoitov
2025-04-25 17:50 ` Alan Maguire
2025-04-25 17:58   ` Andrii Nakryiko
2025-04-25 20:36     ` Alan Maguire
2025-04-25 20:41       ` Andrii Nakryiko
2025-04-26 17:28         ` Alan Maguire
2025-04-28 15:21           ` Alan Maguire
2025-04-28 19:36             ` Arnaldo Carvalho de Melo
2025-04-28 19:50               ` Arnaldo Carvalho de Melo
2025-04-28 22:12             ` Alexei Starovoitov
2025-04-29  0:33               ` Andrii Nakryiko
2025-04-29  6:59                 ` Andrii Nakryiko
2025-04-29 15:37                   ` Andrii Nakryiko
2025-04-29 15:55                     ` Alan Maguire
2025-04-29 19:29                     ` Eduard Zingerman
2025-04-29 19:50                       ` Andrii Nakryiko
2025-04-29 20:34                         ` Eduard Zingerman
2025-04-29 20:55                         ` Alexei Starovoitov
2025-04-29 21:44                           ` Andrii Nakryiko
2025-04-25 20:58     ` Andrii Nakryiko
2025-04-25 18:14 ` Eduard Zingerman
2025-04-25 19:43   ` Eduard Zingerman
2025-04-25 20:16     ` Alexei Starovoitov
2025-04-25 20:25       ` Eduard Zingerman [this message]
2025-04-25 20:30         ` Alexei Starovoitov
2025-04-25 20:30         ` 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=m2r01gf0pn.fsf@gmail.com \
    --to=eddyz87@gmail.com \
    --cc=acme@kernel.org \
    --cc=alan.maguire@oracle.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=dwarves@vger.kernel.org \
    --cc=ihor.solodrai@linux.dev \
    --cc=memxor@gmail.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