aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
diff options
context:
space:
mode:
authorYonghong Song <yhs@fb.com>2020-02-14 16:46:49 -0800
committerYonghong Song <yhs@fb.com>2020-05-15 09:44:54 -0700
commit072cde03aaa13a2c57acf62d79876bf79aa1919f (patch)
tree679d6492b681f88ce0b2f34c3e9cfa9219f7be03 /llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
parent9825d3daa80c19872326d8e137ada39a1727cfe8 (diff)
downloadllvm-072cde03aaa13a2c57acf62d79876bf79aa1919f.zip
llvm-072cde03aaa13a2c57acf62d79876bf79aa1919f.tar.gz
llvm-072cde03aaa13a2c57acf62d79876bf79aa1919f.tar.bz2
[Clang][BPF] implement __builtin_btf_type_id() builtin function
Such a builtin function is mostly useful to preserve btf type id for non-global data. For example, extern void foo(..., void *data, int size); int test(...) { struct t { int a; int b; int c; } d; d.a = ...; d.b = ...; d.c = ...; foo(..., &d, sizeof(d)); } The function "foo" in the above only see raw data and does not know what type of the data is. In certain cases, e.g., logging, the additional type information will help pretty print. This patch implemented a BPF specific builtin u32 btf_type_id = __builtin_btf_type_id(param, flag) which will return a btf type id for the "param". flag == 0 will indicate a BTF local relocation, which means btf type_id only adjusted when bpf program BTF changes. flag == 1 will indicate a BTF remote relocation, which means btf type_id is adjusted against linux kernel or future other entities. Differential Revision: https://reviews.llvm.org/D74668
Diffstat (limited to 'llvm/lib/Bitcode/Writer/BitcodeWriter.cpp')
0 files changed, 0 insertions, 0 deletions