No need for translation unit name header in BTF after all
No need for translation unit name header in BTF after all
Posted Oct 8, 2025 12:29 UTC (Wed) by nix (subscriber, #2304)Parent article: Next steps for BPF support in the GNU toolchain
I've found a way to work around the need for the translation-unit-name header field in BTF (the name is still recorded, but not in a way that requires changes to BTF, so existing users don't need to worry about header changes). (It's ugly, but it works, and backward compatibility is a thing to strive for, etc.)