/usr/bin/foo 的共享庫的 SONAME ：objdump -p /usr/bin/foo | grep NEEDED 2 • libfoo1: 共享庫 libfoo.so.1 的庫文件包，其 SONAME ABI 版本爲 1.3 • 在某些情況下，庫軟件包的 maintainer scripts 必須調用 ldconfig 來爲 SONAME 創建必要的符號鏈接。⁴ 1或者這樣：readelf -d libfoo 管理 debian/package.symbols 當你給共享庫打包時，你應當建立 debian/package.symbols 檔案來管理在共享庫名稱不變，在同一個 SONAME 下又要提供 ABI 向後相容性的情況下每個符號關聯到的最小版本號。⁸ 你可以閱讀下邊的主要參考以獲知細節： • Debian Policy Manual, 8.6.3 ”The symbols system” (http://www -Plibfoo1_1.2-1 -Osymbols • 嘗試用像 debuild 和 pdebuild 這樣的工具來對原始碼樹進行試構建。(如果這因為缺失符號之類原因而失敗，那麼這 裡就有一些不向後相容的 ABI 改變，這就需要你轉移 (bump) 共享庫的名稱到諸如 libfoo1a ，並重新開始一次。） ⁵參見 Debian Policy Manual, 8.3 ”Static libraries” (http://www

any C function might have undefined behaviour under any arbitrary circumstances. 此例中的 "C" 為 ABI；您也可以使用其他 ABI。 編寫不安全的函式 We wouldn't actually use pointers for a swap function - it can be done safely with switch 相關資訊 • 如何在 VSCode 中安裝 rust-analyzer 此範例會探究做為最小公因數的互通語言 C，因此很特別。C++ 和 Rust 都能以原生方式宣告及呼叫 C ABI 函式。本課程稍後會將 C++ 直接連結至 Rust。 這裡需要 allow_unsafe = true，因為#[no_mangle] 可能會允許 Rust 產生兩個名稱相同的函 式，Rust 就不再能保證系統會呼叫正確的函式。 • 這項工具會自動為非 C 功能產生 FFI 替換程式 (與 C-ABI 相容的小型、可自由使用的函式)，例如讓 FFI 呼叫 Rust 或 C++ 方法；手動繫結會需要手動編寫這類頂層的、可自由使用的函式 • 這項工具和程式庫可處理一組核心型別，例如： – &[T] 傳遞時可以跨越 FFI 邊界，但無法保證任何特定 ABI 或記憶體布局。使用手動繫結時， std::span/&[T]

fixed signature. However, while the type layout must be known statically to compute the intended C ABI, the static param- eters of the function are considered to be part of this static environment. The to just indicate rettype is inferred. • ftpr The generic jlcall entry point. • jlcall_api The ABI to use when calling fptr. Some significant ones include: – 0 - Not compiled yet – 1 - JL_CALLABLE backtraces for JIT functions • ccall.cpp Handles the ccall and llvmcall FFI, along with various abi_*.cpp files • intrinsics.cpp Handles the emission of various low-level intrinsic functions Bootstrapping

fixed signature. However, while the type layout must be known statically to compute the intended C ABI, the static param- eters of the function are considered to be part of this static environment. The to just indicate rettype is inferred. • ftpr The generic jlcall entry point. • jlcall_api The ABI to use when calling fptr. Some significant ones include: – 0 - Not compiled yet – 1 - JL_CALLABLE backtraces for JIT functions • ccall.cpp Handles the ccall and llvmcall FFI, along with various abi_*.cpp files • intrinsics.cpp Handles the emission of various low-level intrinsic functions Bootstrapping

fixed signature. However, while the type layout must be known statically to compute the intended C ABI, the static param- eters of the function are considered to be part of this static environment. The to just indicate rettype is inferred. • ftpr The generic jlcall entry point. • jlcall_api The ABI to use when calling fptr. Some significant ones include: – 0 - Not compiled yet – 1 - JL_CALLABLE backtraces for JIT functions • ccall.cpp Handles the ccall and llvmcall FFI, along with various abi_*.cpp files • intrinsics.cpp Handles the emission of various low-level intrinsic functions Bootstrapping

fixed signature. However, while the type layout must be known statically to compute the intended C ABI, the static param- eters of the function are considered to be part of this static environment. The to just indicate rettype is inferred. • ftpr The generic jlcall entry point. • jlcall_api The ABI to use when calling fptr. Some significant ones include: – 0 - Not compiled yet – 1 - JL_CALLABLE backtraces for JIT functions • ccall.cpp Handles the ccall and llvmcall FFI, along with various abi_*.cpp files • intrinsics.cpp Handles the emission of various low-level intrinsic functions Bootstrapping

fixed signature. However, while the type layout must be known statically to compute the intended C ABI, the static param- eters of the function are considered to be part of this static environment. The to just indicate rettype is inferred. • ftpr The generic jlcall entry point. • jlcall_api The ABI to use when calling fptr. Some significant ones include: – 0 - Not compiled yet – 1 - JL_CALLABLE backtraces for JIT functions • ccall.cpp Handles the ccall and llvmcall FFI, along with various abi_*.cpp files • intrinsics.cpp Handles the emission of various low-level intrinsic functions Bootstrapping

fixed signature. However, while the type layout must be known statically to compute the intended C ABI, the static param- eters of the function are considered to be part of this static environment. The generic jlcall entry point.CHAPTER 106. DOCUMENTATION OF JULIA'S INTERNALS 1873 • jlcall_api The ABI to use when calling fptr. Some significant ones include: – 0 - Not compiled yet – 1 - JL_CALLABLE backtraces for JIT functions • ccall.cpp Handles the ccall and llvmcall FFI, along with various abi_*.cpp files • intrinsics.cpp Handles the emission of various low-level intrinsic functions Bootstrapping

fixed signature. However, while the type layout must be known statically to compute the intended C ABI, the static param- eters of the function are considered to be part of this static environment. The to just indicate rettype is inferred. • ftpr The generic jlcall entry point. • jlcall_api The ABI to use when calling fptr. Some significant ones include: – 0 - Not compiled yet – 1 - JL_CALLABLE backtraces for JIT functions • ccall.cpp Handles the ccall and llvmcall FFI, along with various abi_*.cpp files • intrinsics.cpp Handles the emission of various low-level intrinsic functions Bootstrapping

fixed signature. However, while the type layout must be known statically to compute the intended C ABI, the static param- eters of the function are considered to be part of this static environment. The to just indicate rettype is inferred. • ftpr The generic jlcall entry point. • jlcall_api The ABI to use when calling fptr. Some significant ones include: – 0 - Not compiled yet – 1 - JL_CALLABLE backtraces for JIT functions • ccall.cpp Handles the ccall and llvmcall FFI, along with various abi_*.cpp files • intrinsics.cpp Handles the emission of various low-level intrinsic functions Bootstrapping