RISC-V's ld.so assumes the standard calling convention
Checks
Context |
Check |
Description |
dj/TryBot-apply_patch |
success
|
Patch applied to master at the time it was sent
|
dj/TryBot-32bit |
success
|
Build for i686
|
Commit Message
The RISC-V port has always required that lazily bound functions are
compatible with the standard calling convention, so document that
behavior explicitly.
Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
---
There was a long-outstading bug against the psABI that was recently
resolved to a different conclusion thus putting us at odds with the
spec. There's an on-going discussion about how we're going to handle
that divergence, but regardless of which direction that goes we're still
in this spot now so we might as well document it.
---
manual/platform.texi | 3 +++
1 file changed, 3 insertions(+)
@@ -121,6 +121,9 @@ when it is not allowed, the priority is set to medium.
@node RISC-V
@appendixsec RISC-V-specific Facilities
+Functions that are lazily bound must be compatible with the standard calling
+convention.
+
Cache management facilities specific to RISC-V systems that implement the Linux
ABI are declared in @file{sys/cachectl.h}.