From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: James Hilliard <james.hilliard1@gmail.com>,
bpf <bpf@vger.kernel.org>,
david.faust@oracle.com
Subject: Re: bpftool gen object doesn't handle GCC built BPF ELF files
Date: Tue, 02 Aug 2022 17:57:36 +0200 [thread overview]
Message-ID: <874jyubpu7.fsf@oracle.com> (raw)
In-Reply-To: <8735fbcv3x.fsf@oracle.com> (Jose E. Marchesi's message of "Fri, 08 Jul 2022 20:33:38 +0200")
>> For functions GCC generates a BTF_KIND_FUNC entry, which has no linkage
>> information, or so we thought: I just looked at bpftool/btf.c and I
>> found the linkage info for function types is expected to be encoded in
>> the vlen field of BTF_KIND_FUNC entries (why not adding a btf_func
>> instead???) which is surprising to say the least.
>>
>> We are changing GCC to encode the linkage info in vlen for these types.
>> Thanks for reporting this.
>
> Patch sent to GCC upstream:
> https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598090.html
FYI this is now applied in GCC master.
next prev parent reply other threads:[~2022-08-02 15:57 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 17:11 bpftool gen object doesn't handle GCC built BPF ELF files James Hilliard
2022-07-06 17:20 ` Andrii Nakryiko
2022-07-06 17:49 ` James Hilliard
2022-07-08 11:55 ` Jose E. Marchesi
2022-07-08 12:23 ` James Hilliard
2022-07-08 13:46 ` Jose E. Marchesi
2022-07-08 13:53 ` James Hilliard
2022-07-08 14:39 ` Jose E. Marchesi
2022-07-08 14:51 ` Jose E. Marchesi
2022-07-08 18:33 ` Jose E. Marchesi
2022-07-08 20:59 ` James Hilliard
2022-07-09 17:24 ` Jose E. Marchesi
2022-07-09 17:28 ` James Hilliard
2022-07-09 20:20 ` Jose E. Marchesi
2022-07-09 20:32 ` James Hilliard
2022-07-09 20:39 ` James Hilliard
2022-07-09 22:41 ` Jose E. Marchesi
2022-07-09 22:54 ` James Hilliard
2022-07-10 9:38 ` Jose E. Marchesi
2022-07-10 12:16 ` James Hilliard
2022-07-10 13:06 ` Jose E. Marchesi
2022-07-10 19:49 ` Jose E. Marchesi
2022-07-10 20:22 ` Jose E. Marchesi
2022-07-11 1:55 ` Jose E. Marchesi
[not found] ` <CADvTj4o-36iuru665BW0XnEauXBeszW438QTtpt4_VUEjf5nXg@mail.gmail.com>
2022-08-01 22:51 ` Andrii Nakryiko
2022-08-01 23:35 ` James Hilliard
2022-08-02 21:28 ` Andrii Nakryiko
2022-08-02 22:05 ` James Hilliard
2022-08-03 0:29 ` Andrii Nakryiko
2022-08-03 1:49 ` James Hilliard
2022-08-03 16:57 ` Andrii Nakryiko
2022-08-03 19:24 ` James Hilliard
2022-09-30 21:52 ` James Hilliard
2022-09-30 22:50 ` Andrii Nakryiko
2022-08-04 17:29 ` Alexei Starovoitov
2022-08-02 15:57 ` Jose E. Marchesi [this message]
2022-07-12 0:34 ` Indu Bhagat
2022-07-13 4:28 ` 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=874jyubpu7.fsf@oracle.com \
--to=jose.marchesi@oracle.com \
--cc=andrii.nakryiko@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=david.faust@oracle.com \
--cc=james.hilliard1@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