Closed ismaeldamiao closed 1 week ago
Simple, because this is a compiler dependent feature, but is reasonable to suppose that any compiler targeting RISC-V have support to RISC-V C API language extensions.
This is probably a solution in search of a problem, but couldn't we just mandate that, as part of the RISC-V C API, the __BYTE_ORDER__
etc. macros be defined?
It reflects reality, after all.
In fact, looks better.
The RISC-V ELF Specification allow both big-endian and little-endian but there is no macro on RISC-V C API to check the host endianness.