Skip to content

Commit bf3aca5

Browse files
zero registers is also an option
Co-authored-by: Dante Broggi <[email protected]>
1 parent 4c556e0 commit bf3aca5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

reference/src/glossary.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
[abi]: #abi-of-a-type
55

66
The *function call ABI* or short *ABI* of a type defines how it is passed *by-value* across a function boundary.
7-
Possible ABIs include passing the value directly in one or more registers, or passing it indirectly as a pointer to the actual data.
7+
Possible ABIs include passing the value directly in zero or more registers, or passing it indirectly as a pointer to the actual data.
88
The space of all possible ABIs is huge and extremely target-dependent.
99
Rust therefore does generally not clearly define the ABI of any type, it only defines when two types are *ABI-compatible*,
1010
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`.

0 commit comments

Comments
 (0)