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: Thu, 01 Dec 2022 17:09:21 +0000 [thread overview] Message-ID: <bug-106773-4-8sBFHlIC64@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 #8 from David Faust <david.faust at oracle dot com> --- (In reply to James Hilliard from comment #5) > (In reply to David Faust from comment #4) > > Created attachment 53993 [details] > > proposed patch > > > > Should fix the remaining issues with 'extern' linkage and the missing > > 'const' modifier (and includes the earlier partial fixes in this bug) > > Fixes the reported test failure but some others(unclear if related to this > bug) are still failing such as tailcall_bpf2bpf3.c: Thanks for testing and confirming. > $ /home/buildroot/bpf-next/tools/testing/selftests/bpf/tools/sbin/bpftool > --debug gen object > /home/buildroot/bpf-next/tools/testing/selftests/bpf/bpf_gcc/ > tailcall_bpf2bpf3.bpf.linked1.o > /home/buildroot/bpf-next/tools/testing/selftests/bpf/bpf_gcc/ > tailcall_bpf2bpf3.bpf.o > libbpf: linker: adding object file > '/home/buildroot/bpf-next/tools/testing/selftests/bpf/bpf_gcc/ > tailcall_bpf2bpf3.bpf.o'... > libbpf: failed to find BTF info for global/extern symbol 'llvm.bpf.load.word' > Error: failed to link > https://github.com/torvalds/linux/blob/v6.1-rc7/tools/testing/selftests/bpf/bpf_legacy.h unsigned long long load_word(void *skb, unsigned long long off) asm("llvm.bpf.load.word"); Looks like LLVM-specific inline asm to use their llvm.bpf.load.word intrinsic. GCC has equivalent __builtin_load_{byte,half,word} target builtins. > There's also this error during skeleton generation for kfunc_call_test.c: > ... > libbpf: failed to find BTF for extern 'bpf_kfunc_call_test2': -22 Hm, looks like we are OK for extern variables but are mis-generating something (or missing something) for extern funcs still. Will look into this.
next prev parent reply other threads:[~2022-12-01 17:09 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 [this message] 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-8sBFHlIC64@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).