Skip to content

Commit

Permalink
zero registers is also an option
Browse files Browse the repository at this point in the history
Co-authored-by: Dante Broggi <[email protected]>
  • Loading branch information
RalfJung and Dante-Broggi authored Sep 8, 2023
1 parent 4c556e0 commit bf3aca5
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion reference/src/glossary.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
[abi]: #abi-of-a-type

The *function call ABI* or short *ABI* of a type defines how it is passed *by-value* across a function boundary.
Possible ABIs include passing the value directly in one or more registers, or passing it indirectly as a pointer to the actual data.
Possible ABIs include passing the value directly in zero or more registers, or passing it indirectly as a pointer to the actual data.
The space of all possible ABIs is huge and extremely target-dependent.
Rust therefore does generally not clearly define the ABI of any type, it only defines when two types are *ABI-compatible*,
which means that it is legal to call a function declared with an argument or return type `T` using a declaration or function pointer with argument or return type `U`.
Expand Down

0 comments on commit bf3aca5

Please sign in to comment.