mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

linking in general has more pitfalls than just call ABI

Browse Source
This commit is contained in:
Ralf Jung 2023-11-17 08:02:28 +01:00
parent 52d22eaa23
commit 8f03a55566
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
library/core/src/primitive_docs.rs
View File

@ -1521,8 +1521,9 @@ mod prim_ref {}
/// exceptional circumstances. Most Rust code just imports functions via `use`. `#[target_feature]` /// exceptional circumstances. Most Rust code just imports functions via `use`. `#[target_feature]`
/// is also used rarely. So, most likely you do not have to worry about ABI compatibility. /// is also used rarely. So, most likely you do not have to worry about ABI compatibility.
/// ///
/// But assuming such circumstances, what are the rules? For this section, we are specifically /// But assuming such circumstances, what are the rules? For this section, we are only considering
/// concerned with the case where both the caller and the callee are defined in Rust. /// the ABI of direct Rust-to-Rust calls, not linking in general -- once functions are imported via
/// `extern` blocks, there are more things to consider that we do not go into here.
/// ///
/// For two signatures to be considered *ABI-compatible*, they must use a compatible ABI string, /// For two signatures to be considered *ABI-compatible*, they must use a compatible ABI string,
/// must take the same number of arguments, the individual argument types and the return types must /// must take the same number of arguments, the individual argument types and the return types must