AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 18 Bitcoin

build: set CMAKE_VISIBILITY_INLINES_HIDDEN in REDUCE_EXPORTS

Public commit record

What the developer wrote

Authored by fanquake

100/100 · Strong
build: set CMAKE_VISIBILITY_INLINES_HIDDEN in REDUCE_EXPORTS

This was originally part of the CMake switchover, but was removed
because it was an addition, rather than a port. Add it now.

> This switch declares that the user does not attempt to compare pointers
> to inline functions or methods where the addresses of the two functions
> are taken in different shared objects.

> The effect of this is that GCC may, effectively, mark inline methods
> with __attribute__ ((visibility ("hidden"))) so that they do not appear
> in the export table of a DSO

See https://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Dialect-Options.html.

See also
https://cmake.org/cmake/help/latest/prop_tgt/VISIBILITY_INLINES_HIDDEN.html.

Co-authored-by: Hennadii Stepanov <32963518+hebasto@users.noreply.github.com>
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This is a build-system hardening change for Bitcoin Core. It tells the compiler to hide inline C++ functions from the list of symbols exported by shared libraries and executables. This reduces the attack surface by making fewer internal functions visible to outside code, but it is not a fix for a known exploitable bug.

Recommended action

No urgent action required. Treat as routine build hardening. Users building from source with REDUCE_EXPORTS (default where supported) will automatically gain reduced symbol exposure. Review downstream release notes for any mention of ABI or plugin compatibility concerns.

Security signals we found

01

Defense-in-depth symbol visibility reduction

02

Build hardening, not a runtime vulnerability fix

03

No functional code change

04

No CVE or advisory referenced in commit

Risk score

Why this scored 18/100

Our methodology →
Potential impact 2/30
Exploitability 1/25
Stealth signal 1/15
Affected reach 2/15
Confidence 8/10
Evidence quality 4/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.