public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106773] libbpf: failed to find BTF info for global/extern symbol 'bpf_link_fops'
Date: Wed, 14 Dec 2022 18:26:03 +0000 [thread overview]
Message-ID: <bug-106773-4-h8LgYqRk8J@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106773-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106773
--- Comment #19 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by David Faust <dfaust@gcc.gnu.org>:
https://gcc.gnu.org/g:70b303049e45c180236a4114f844311652bad002
commit r13-4709-g70b303049e45c180236a4114f844311652bad002
Author: David Faust <david.faust@oracle.com>
Date: Wed Dec 7 11:51:59 2022 -0800
btf: correct generation for extern funcs [PR106773]
The eBPF loader expects to find entries for functions declared as extern
in the corresponding BTF_KIND_DATASEC record, but we were not generating
these entries.
This patch adds support for the 'extern' linkage of function types in
BTF, and creates entries for for them BTF_KIND_DATASEC records as needed.
PR target/106773
gcc/
* btfout.cc (get_section_name): New function.
(btf_collect_datasec): Use it here. Process functions, marking them
'extern' and generating DATASEC entries for them as appropriate.
Move
creation of BTF_KIND_FUNC records to here...
(btf_dtd_emit_preprocess_cb): ... from here.
gcc/testsuite/
* gcc.dg/debug/btf/btf-datasec-2.c: New test.
* gcc.dg/debug/btf/btf-function-6.c: New test.
include/
* btf.h (enum btf_func_linkage): New.
(struct btf_var_secinfo): Update comments with notes about extern
functions.
next prev parent reply other threads:[~2022-12-14 18:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 22:07 [Bug c/106773] New: " james.hilliard1 at gmail dot com
2022-09-01 20:31 ` [Bug target/106773] " james.hilliard1 at gmail dot com
2022-09-01 22:33 ` james.hilliard1 at gmail dot com
2022-11-29 0:44 ` david.faust at oracle dot com
2022-11-30 21:20 ` david.faust at oracle dot com
2022-12-01 0:04 ` james.hilliard1 at gmail dot com
2022-12-01 0:12 ` james.hilliard1 at gmail dot com
2022-12-01 2:07 ` james.hilliard1 at gmail dot com
2022-12-01 17:09 ` david.faust at oracle dot com
2022-12-01 21:49 ` david.faust at oracle dot com
2022-12-01 22:09 ` james.hilliard1 at gmail dot com
2022-12-01 22:11 ` james.hilliard1 at gmail dot com
2022-12-01 22:30 ` james.hilliard1 at gmail dot com
2022-12-05 17:42 ` david.faust at oracle dot com
2022-12-05 19:01 ` james.hilliard1 at gmail dot com
2022-12-05 21:06 ` david.faust at oracle dot com
2022-12-05 21:57 ` james.hilliard1 at gmail dot com
2022-12-14 18:25 ` cvs-commit at gcc dot gnu.org
2022-12-14 18:25 ` cvs-commit at gcc dot gnu.org
2022-12-14 18:26 ` cvs-commit at gcc dot gnu.org [this message]
2023-01-06 14:18 ` jemarch at gcc dot gnu.org
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=bug-106773-4-h8LgYqRk8J@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).