iwyu: Fix patch to prefer `<cstdint>`
What the developer wrote
Authored by Hennadii Stepanov
iwyu: Fix patch to prefer `<cstdint>`
The goal of the patch is to suggest C++ headers rather than their C
counterparts. However, for fixed width integer types, the patched IWYU
currently suggests `<cinttypes>` where `<cstdint>` is sufficient.
This change fixes this behavior.
What changed, and why it matters
This commit updates a patch file used in Bitcoin Core's continuous integration (CI) tooling. The patch guides an automated code-style checker (include-what-you-use) to recommend modern C++ headers like <cstdint> instead of older C-style headers. It does not change any Bitcoin Core runtime code, consensus logic, or network behavior, and has no direct security impact on users.
No security action required. Treat as a normal CI/maintenance tooling fix.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The change is in ci/test/01_iwyu.patch, which patches the include-what-you-use (IWYU) tool used in CI. It corrects an include-mapping rule so that fixed-width integer types map to
Changed components
ci/test/01_iwyu.patchInspect captured patch +1 / −1
diff --git a/ci/test/01_iwyu.patch b/ci/test/01_iwyu.patch
index e7d75f4e..209e133f 100644
--- a/ci/test/01_iwyu.patch
+++ b/ci/test/01_iwyu.patch
@@ -535,7 +535,7 @@ See: https://github.com/include-what-you-use/include-what-you-use/blob/clang_21/
{ "<sys/ustat.h>", kPrivate, "<ustat.h>", kPublic },
// Exports guaranteed by the C standard
- { "<stdint.h>", kPublic, "<inttypes.h>", kPublic },
-+ { "<stdint.h>", kPrivate, "<inttypes.h>", kPrivate },
++ { "<cstdint>", kPublic, "<cinttypes>", kPublic },
};
const IncludeMapEntry stdlib_c_include_map[] = {
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.