public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ibhagat at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/112656] btf: function prototypes generated with name Date: Mon, 27 Nov 2023 21:43:36 +0000 [thread overview] Message-ID: <bug-112656-4-puWIC81OsA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112656-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112656 Indu Bhagat <ibhagat at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ibhagat at gcc dot gnu.org --- Comment #4 from Indu Bhagat <ibhagat at gcc dot gnu.org> --- Noted that the issue is not repeatable on x86_64. $ cat foo.c static int log_event(const char *event_name, void *dev_ptr) { return 666; } int foo () { return log_event ("foobar", ((void *)0)); } $ gcc -O2 -gbtf -c foo.c $ bpftool btf dump file foo.o [1] INT 'int' size=4 bits_offset=0 nr_bits=32 encoding=SIGNED [2] FUNC_PROTO '(anon)' ret_type_id=1 vlen=0 [3] FUNC_PROTO '(anon)' ret_type_id=1 vlen=2 'event_name' type_id=6 'dev_ptr' type_id=7 [4] INT 'char' size=1 bits_offset=0 nr_bits=8 encoding=SIGNED [5] CONST '(anon)' type_id=4 [6] PTR '(anon)' type_id=5 [7] PTR '(anon)' type_id=0 [8] FUNC 'foo' type_id=2 linkage=global [9] FUNC 'log_event' type_id=3 linkage=static
next prev parent reply other threads:[~2023-11-27 21:43 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-21 19:25 [Bug debug/112656] New: " jemarch at gcc dot gnu.org 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 [this message] 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-puWIC81OsA@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).