...as a non-standard feature, so it will not be enabled for
"--btf_features=all"
Signed-off-by: Alan Maguire <alan.maguire@xxxxxxxxxx>
---
man-pages/pahole.1 | 8 ++++++++
pahole.c | 1 +
2 files changed, 9 insertions(+)
diff --git a/man-pages/pahole.1 b/man-pages/pahole.1
index 2c08e97..64de343 100644
--- a/man-pages/pahole.1
+++ b/man-pages/pahole.1
@@ -310,6 +310,14 @@ Encode BTF using the specified feature list, or specify 'all' for all standard f
in different CUs.
.fi
+Supported non-standard features (not enabled for 'all')
+
+.nf
+ reproducible_build Ensure generated BTF is consistent every time;
+ without this parallel BTF encoding can result in
+ inconsistent BTF ids.
+.fi
+
So for example, specifying \-\-btf_encode=var,enum64 will result in a BTF encoding that (as well as encoding basic BTF information) will contain variables and enum64 values.
.TP
diff --git a/pahole.c b/pahole.c
index 890ef81..38cc636 100644
--- a/pahole.c
+++ b/pahole.c
@@ -1286,6 +1286,7 @@ struct btf_feature {
BTF_FEATURE(enum64, skip_encoding_btf_enum64, true, true),
BTF_FEATURE(optimized_func, btf_gen_optimized, false, true),
BTF_FEATURE(consistent_func, skip_encoding_btf_inconsistent_proto, false, true),
+ BTF_FEATURE(reproducible_build, reproducible_build, false, false),
};
#define BTF_MAX_FEATURE_STR 1024
--
2.39.3
