public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jemarch at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/112656] New: btf: function prototypes generated with name Date: Tue, 21 Nov 2023 19:25:44 +0000 [thread overview] Message-ID: <bug-112656-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112656 Bug ID: 112656 Summary: btf: function prototypes generated with name Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug Assignee: unassigned at gcc dot gnu.org Reporter: jemarch at gcc dot gnu.org Target Milestone: --- BTF suports both BTF_KIND_FUNC and BTF_KIND_FUNC_PROTO tags. FUNC entries link to their corresponding PROTO via type_id. PROTO entries must have no names, i.e. name_off shall be 0. GCC seems to be generating non-anonymous BTF_KIND_FUNC_PROTO entries in some circumstances: $ bpf-unknown-none-gcc -c -O2 repro.i -o repro.o $ bpftool btf dump all | grep FUNC_PROTO | grep -v anon [8319] FUNC_PROTO '____kretprobe_ieee80211_get_channel_khz' ret_type_id=7 vlen=2 [8321] FUNC_PROTO '____kprobe_ieee80211_scan_completed' ret_type_id=7 vlen=2 [8333] FUNC_PROTO '____kprobe_ieee80211_request_scan' ret_type_id=7 vlen=2 [8343] FUNC_PROTO '____kprobe_unregister_netdev' ret_type_id=7 vlen=2 [8345] FUNC_PROTO '____kprobe_register_netdev' ret_type_id=7 vlen=2 [8347] FUNC_PROTO '____kprobe_ieee80211_unregister_hw' ret_type_id=7 vlen=1 [8349] FUNC_PROTO '____kprobe_ieee80211_register_hw' ret_type_id=7 vlen=1 [8351] FUNC_PROTO 'log_event' ret_type_id=0 vlen=2
next reply other threads:[~2023-11-21 19:25 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-21 19:25 jemarch at gcc dot gnu.org [this message] 2023-11-21 19:37 ` [Bug debug/112656] " jemarch at gcc dot gnu.org 2023-11-21 19:45 ` jemarch at gcc dot gnu.org 2023-11-21 20:37 ` jemarch at gcc dot gnu.org 2023-11-27 21:43 ` ibhagat at gcc dot gnu.org 2023-11-27 21:53 ` ibhagat at gcc dot gnu.org 2023-11-28 5:15 ` jemarch at gcc dot gnu.org 2023-11-29 19:07 ` ibhagat at gcc dot gnu.org 2023-12-04 10:01 ` cvs-commit 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-112656-4@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).