Spent most of my work day yesterday debugging Mono's JIT in an arm32v5 environment. Conclusion: it's super broken and needs a lot of work. Also I'm going to do it because if Debian still supports it then so can I.
@lewurm That's the one. I ran the tests with the optimization disabled, and it's still broken. I'm like 90% sure it's spilling doubles into 4-byte stack slots.
@madewokherd ah, just saw you figured out quite some stuff already in the linked gitlab ticket.
only thing I can do for you is to pray to the ABI gods I guess 😅 I don't remember all the details, but on _some_ platforms LLVM is used in the backend when AOT compiling, causing additional complications. there was one fix in that area before I left the project: https://github.com/mono/mono/pull/11621
can't say anymore if armv5 was one of those platforms.
anyway, your most recent issue looks like something else
@madewokherd ah, just saw you figured out quite some stuff already in the linked gitlab ticket.
only thing I can do for you is to pray to the ABI gods I guess 😅 I don't remember all the details, but on _some_ platforms LLVM is used in the backend when AOT compiling, causing additional complications. there was one fix in that area before I left the project: https://github.com/mono/mono/pull/11621
can't say anymore if armv5 was one of those platforms.
anyway, your most recent issue looks like something else