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/107480] New: bpf: add __builtin_preserve_type_info
Date: Mon, 31 Oct 2022 20:27:24 +0000 [thread overview]
Message-ID: <bug-107480-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107480
Bug ID: 107480
Summary: bpf: add __builtin_preserve_type_info
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: david.faust at oracle dot com
Target Milestone: ---
LLVM supports a BPF builtin:
__builtin_preserve_type_info (param, flag)
which is used to generate additional relocations for the
Compile Once - Run Everywhere (CO-RE) mechanism.
This builtin produces a relocation recording the information
about the type of 'param', such as it's size or whether or
not it exists on the host kernel, according to 'flag'. This
information is returned to the program and patched by the
eBPF loader during loading.
We should support this functionality in GCC.
These are the relevant changes in LLVM:
https://reviews.llvm.org/D83878
https://reviews.llvm.org/D83242
next reply other threads:[~2022-10-31 20:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 20:27 david.faust at oracle dot com [this message]
2023-04-19 16:36 ` [Bug target/107480] " jemarch at gcc dot gnu.org
2023-08-03 18:50 ` cvs-commit at gcc dot gnu.org
2023-10-31 19:52 ` 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-107480-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: 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).