3 - Support for DW_TAG_unspecified_type more generally, that in binutils 2.40 is used
4 for assembly functions, resulting in BTF encoding problems when building the Linux
7 - Make sure struct member offsets are in ascending order. This is part of the set of
8 changes to support encoding BTF for Rust for use with the Linux kernel, where the
9 BTF verifier considers invalid offset unordered struct members.
11 - Support C atomic types (DW_TAG_atomic_type), that are not used in the Linux kernel but
12 is present in user space components such as Open VSwitch.
16 - Initial support for DW_TAG_LLVM_annotation, used for BTF type tags, to encode things
17 like __rcu, __user annotations in the Linux kernel. This is still in flux with changes
18 in how these are encoded that resulted from the discussion to support this in gcc in
19 addition to in clang, where it was first designed.
23 - Exclude functions with the same name (static functions in different CUs),
24 inconsistent prototypes or not following calling convention.
26 - Allow generation of BTF for optimized functions, those that end with a .isra*
27 suffix (inter procedural scalar replacement of aggregates) or .constprop*
28 (constant propagation).
32 - For now the DW_TAG_LLVM_annotation tags are being suppressed, so the output from
33 BTF and DWARF matches, further work is planned to support it so that the output
34 matches the original source code and can be recompilable, resulting in the same
37 - Support C atomic types, allowing the generation of source code that can be
38 compiled with resulting DWARF info matching the original source code.
42 - Support --lang=/--lang_exclude=asm, the DW_LANG_ define for assembly is out
43 of order, special case it to support asking for CUs written in assembly to be
46 - Support suppressing the atomic type modifiers/attributes.
48 - Allow filtering out functions optimized by the compiler, where the calling convention isn't
49 the one expected by BPF or arguments are optimized out.
51 - Support --compile from DWARF in addition to from BTF, this allows user space components
52 such as Open VSwitch to use pahole to generate compilable code for its data structures.
56 - Exclude RUST CUs, as those are not yet being BTF encoded.
58 Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>