[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fU29TwcbsHhOzgUSV4QDa4RrsundXmcr3i6FGXdqvslY":3},{"item":4,"related":48},{"id":5,"type":6,"title":7,"slug":8,"summary":9,"body":10,"coverUrl":11,"productScreenshots":12,"productLinks":13,"authorName":14,"authorUrl":15,"authorSubject":16,"category":17,"tags":22,"sourceLabel":39,"sourceName":40,"sourceUrl":41,"status":42,"seoTitle":7,"seoDescription":9,"canonicalUrl":39,"isFeatured":43,"sno":44,"sortOrder":45,"publishedAt":46,"updatedAt":47,"createdAt":47},"d0700249-defa-43a1-a66a-4455c6889072","article","ABI：为什么源码能编译，二进制却不能互相调用？","application-binary-interface-abi-explained","ABI 是二进制世界的调用合同，规定参数传递、对象布局、符号命名和异常处理。本文区分 ABI 与 API，解释动态库、C++ 兼容性和跨语言绑定为什么不能只看函数签名。","源码能编译通过，并不代表两个二进制模块就能互相调用。它们还必须同意一套更底层的规则：参数放在哪里、返回值如何传递、对象怎么布局、函数如何命名、异常怎样跨边界传播。这套规则就是 ABI，Application Binary Interface，应用二进制接口。\n\n## ABI 像二进制世界的合同\n\n源代码层面，两个函数都可以叫 `process`；到了链接阶段，编译器必须把它们变成可区分的符号。C++ 还涉及命名修饰、虚函数表、继承对象布局、构造与析构，以及异常处理。只要编译器、标准库、编译选项或目标平台对这些规则的理解不一致，程序就可能链接失败，或者更危险地，在运行时悄悄读错内存。\n\nC 之所以常被用作跨语言接口，是因为它的 ABI 规则相对简单、稳定、覆盖面广。C++ 的对象模型更复杂，不同编译器之间往往不能随意传递带有复杂布局的类。工程上常见的做法是把边界收窄为 C 风格函数、明确宽度的整数、指针和由调用方约定的内存管理。\n\n## ABI 和 API 有什么区别\n\nAPI 是程序员看到的接口：函数名、参数语义、返回值和文档。ABI 是机器看到的接口：寄存器、栈、符号、布局和调用约定。API 不变，重新编译后 ABI 也可能变化；API 变化很小，ABI 却可能因为结构体增加字段而不兼容。\n\n这也是动态库升级需要谨慎的原因。二进制兼容通常要求旧程序无需重新编译也能继续调用新库。稳定 ABI 的设计，往往会隐藏内部结构、提供不透明句柄，并用版本化函数或能力查询控制演进。\n\n## AI 编程为什么值得了解\n\nAI 生成跨语言绑定时，很容易只关注函数签名，却忽略所有权、对齐、异常、线程安全和释放责任。理解 ABI 后，你会知道“能编译”只是第一关，真正要确认的是两边对每一字节的解释是否一致。\n\n## 读者应该记住\n\nAPI 面向人，ABI 面向二进制。跨语言调用、插件系统、动态库、操作系统接口和编译器升级，最终都要落到 ABI 这份底层合同上。\n\n资料：[Itanium C++ ABI](https:\u002F\u002Fitanium-cxx-abi.github.io\u002Fcxx-abi\u002Fabi.html)","\u002Fuploads\u002F2026-09-20\u002F33666a48-4e8f-42a3-9ffd-f4c490498689.jpg",[],[],"Foundit","https:\u002F\u002Ffoundit.cn","foundit-ai-editorial",{"id":18,"name":19,"slug":20,"description":21},"6179d3b6-dc34-4483-9ded-3cd9f1b37a47","科普","abbreviation","介绍各领域新兴概念",[23,27,31,35],{"id":24,"name":25,"slug":26},"144abe77-0dc6-4f66-a176-20bddb1c0bfa","编程","coding",{"id":28,"name":29,"slug":30},"a202d639-99a6-488a-a712-4d4c6ffd7e15","开发","dev",{"id":32,"name":33,"slug":34},"7c76bfc2-f80f-4ee0-a95d-27bd8708b434","技术","slug",{"id":36,"name":37,"slug":38},"4c2bbea6-eab7-40a8-8447-1de478ff7749","分析","analyse",null,"Itanium C++ ABI","https:\u002F\u002Fitanium-cxx-abi.github.io\u002Fcxx-abi\u002Fabi.html","published",false,42,0,"2026-09-20T00:00:00.000Z","2026-09-20T03:58:01.058Z",[49,57,65],{"id":50,"type":6,"title":51,"slug":52,"summary":53,"coverUrl":54,"authorName":14,"sno":55,"publishedAt":46,"createdAt":56},"c9f4e936-9533-4b9c-a1de-f03ef09fed37","WAL：为什么数据库要先写日志，再写真正数据？","write-ahead-logging-wal-database-explained","WAL 要求描述数据变化的日志先于数据页持久化，让数据库可以延迟刷写并在崩溃后通过重放恢复。本文用账本和收据解释 REDO、检查点、复制与持久性设置的关系。","\u002Fuploads\u002F2026-09-20\u002F6260c953-345b-4c9d-b3d6-6202c7e5539c.jpg",43,"2026-09-20T03:58:15.082Z",{"id":58,"type":6,"title":59,"slug":60,"summary":61,"coverUrl":62,"authorName":14,"sno":63,"publishedAt":46,"createdAt":64},"41d50774-50df-4e2f-b1b3-ab6d9f329726","Backpressure：生产者太快时，系统怎样不被数据淹没？","backpressure-reactive-streams-explained","Backpressure 让下游处理能力反过来影响上游生产速度，避免异步流水线靠无限缓存硬撑。本文用水管和阀门解释响应式流、需求信号、数据丢弃与容量设计，也说明它和普通限流的区别。","\u002Fuploads\u002F2026-09-20\u002F35c47792-3d4b-46ae-9375-c68e4c53330e.jpg",45,"2026-09-20T03:58:08.835Z",{"id":66,"type":6,"title":67,"slug":68,"summary":69,"coverUrl":70,"authorName":14,"sno":71,"publishedAt":46,"createdAt":72},"cd4e2aae-cbf2-4428-aab0-a6fa7911a424","Type Erasure：泛型信息为什么运行时消失了？","type-erasure-java-generics-explained","Java 的类型擦除让泛型主要承担编译期检查，生成字节码时把参数化类型替换为上界，并插入必要的转换。本文解释它带来的兼容性优势、反射限制，以及它和 Rust 单态化路线的区别。","\u002Fuploads\u002F2026-09-20\u002Fad612fe0-a1dd-4c46-a5dc-2ddfedefb22d.jpg",46,"2026-09-20T03:57:57.276Z"]