aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/ScriptInterpreter/Python/ScriptedPythonInterface.h
diff options
context:
space:
mode:
authorYonghong Song <yhs@fb.com>2021-11-07 20:36:52 -0800
committerYonghong Song <yhs@fb.com>2021-11-09 11:34:25 -0800
commit8d499bd5bc1eee4c385b2bda26fc5f415a621207 (patch)
treef90cfb1a8e14ae15f32c5d9867f2dc7b5dc2efd8 /lldb/source/Plugins/ScriptInterpreter/Python/ScriptedPythonInterface.h
parent791baf38e14bfbaf56f5ec24a33b232a0a58fad6 (diff)
downloadllvm-8d499bd5bc1eee4c385b2bda26fc5f415a621207.zip
llvm-8d499bd5bc1eee4c385b2bda26fc5f415a621207.tar.gz
llvm-8d499bd5bc1eee4c385b2bda26fc5f415a621207.tar.bz2
BPF: change btf_type_tag BTF output format
For the declaration like below: int __tag1 * __tag1 __tag2 *g Commit 41860e602aaa ("BPF: Support btf_type_tag attribute") implemented the following encoding: VAR(g) -> __tag1 --> __tag2 -> pointer -> __tag1 -> pointer -> int Some further experiments with linux btf_type_tag support, esp. with generating attributes in vmlinux.h, and also some internal discussion showed the following format is more desirable: VAR(g) -> pointer -> __tag2 -> __tag1 -> pointer -> __tag1 -> int The format makes it similar to other modifier like 'const', e.g., const int *g which has encoding VAR(g) -> PTR -> CONST -> int Differential Revision: https://reviews.llvm.org/D113496
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptedPythonInterface.h')
0 files changed, 0 insertions, 0 deletions