iwyu: Document mappings for libc symbols
What the developer wrote
Authored by Hennadii Stepanov
iwyu: Document mappings for libc symbols
What changed, and why it matters
This commit adds a comment and a reference link to a developer tooling file that maps C library symbols to their correct header files. It does not change any executable code, network behavior, or wallet logic. There is no security relevance.
No action needed. This is a documentation-only tooling change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The change is a single-line comment in contrib/devtools/iwyu/bitcoin.core.imp, an Include What You Use (IWYU) mapping file used only for static include cleanup. It documents why libc symbol mappings are present by linking to an upstream IWYU issue. No code, build rules, or dependencies were modified.
Changed components
contrib/devtools/iwyu/bitcoin.core.impInspect captured patch +1 / −0
diff --git a/contrib/devtools/iwyu/bitcoin.core.imp b/contrib/devtools/iwyu/bitcoin.core.imp
index 90d65bea..960cb05d 100644
--- a/contrib/devtools/iwyu/bitcoin.core.imp
+++ b/contrib/devtools/iwyu/bitcoin.core.imp
@@ -6,6 +6,7 @@
{ "include": [ "<tmmintrin.h>", "private", "<immintrin.h>", "public" ] },
# libc symbols.
+ # See: https://github.com/include-what-you-use/include-what-you-use/issues/1809.
{ "symbol": ["AT_HWCAP", "private", "<sys/auxv.h>", "public"] },
{ "symbol": ["AT_HWCAP2", "private", "<sys/auxv.h>", "public"] },
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.