public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "david.faust at oracle dot com" <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: Tue, 29 Nov 2022 00:44:00 +0000 [thread overview] Message-ID: <bug-106773-4-yagosMcipf@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 #3 from David Faust <david.faust at oracle dot com> --- There are two remaining issues: 1. We are missing support for 'linkage=extern' encoding for variables, so 'bpf_link_fops' and others are incorrectly marked with 'linkage=global' instead. 2. 'bpf_link_fops' variable is encoded as 'void' type not 'const void'. This is a result of the BTF being generated from internal DWARF representation. The distinction seems to be intentionally removed in dwarf2out.cc:add_type_attribute(), with the later side-effect that looking up the type DIE for the variable when generating BTF actually fails and falls back to the default 'void'. I have an implementation for (1) in progress. For (2) I need to understand why the 'void'/'const void' distinction is removed in DWARF and how to work around it.
next prev parent reply other threads:[~2022-11-29 0:44 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 [this message] 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 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-yagosMcipf@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: linkBe 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).