Earlier quoted context omitted.
The code generation has been pretty good upstream for many years now. It's easy enough The hardest part of adding full support for RISC-V is to support the hardware floating point ABI. It's incredibly complicated for likely no real world reason. It will likely require a ton of code still to make freepascal fully compliant The software and ABI ecosystem of RISC-V is what made me personally lose my love for it. The ISA…
> It's incredibly complicated for likely no real world reason Can you explain or link to somewhere to read about this? Isn't psABI quite simple?
It's that structs of two simple fields need to be passed in registers. And more specifically that this rule is relevant for mixed integer and floating point fields.
It's a very specific rule that requires a ton of code to implement compared to the integer calling convention. And again like the weird AMD64 convention likely invented to squeeze out a theoretical few cycles that never occur outside microbenchmarks