Developer knowledge network ยท moderated exchange

Onbetrouwbare Code-gemeenschap

Ontwikkelaarsonderzoek, reverse engineering en coderingsgemeenschap

Knowledge indexLive
4Categories
919Threads
2.8KBerichten
Subforums Leiderbord Log in om te posten
Discussion

Understanding C++ Name Mangling, extern "C", and ABI Compatibility [StackOverflow Architecture Guide]

llvm_compiler_dev
LLVM & Clang Hacker
MEMBER
Vertegenwoordiger: 139
Datum van deelname: Jul 2018
Berichten: 21
Bedankt: 15
3 weken geleden ยท Jul 30, 2026 2:44 AM
#1

Why C++ functions cannot be linked directly by C programs without extern "C":

To support function overloading, the C++ compiler encodes parameter types into the compiled symbol name (e.g. void Print(int) becomes _Z5Printi in Itanium ABI or ?Print@@YAXH@Z in MSVC).

Adding extern "C" instructs the C++ compiler to use standard C linkage (plain unmangled symbol Print), allowing dynamic linkers (dlopen / dlsym / GetProcAddress) to find the function across language boundaries.

vtable_slayer
Senior Reverser
MEMBER
Vertegenwoordiger: 215
Datum van deelname: Mar 2018
Berichten: 86
Bedankt: 61
3 weken geleden ยท Jul 30, 2026 7:27 AM
#2

Always wrap public C++ header exports in #ifdef __cplusplus extern "C" { #endif blocks for cross-language compatibility.

assembly_micro_dev
x86_64 Micro-arch
MEMBER
Vertegenwoordiger: 186
Datum van deelname: Oct 2021
Berichten: 10
Bedankt: 27
3 weken geleden ยท Jul 30, 2026 10:46 PM
#3

Essential knowledge when creating shared libraries exported to Python, C#, or Rust.