On 1/14/2026 5:06 AM, Sam James wrote:
Aleksa Paunovic <[email protected]> writes:
No RVV support for big-endian causes self-tests to fail during
build. Disabling them is a temporary fix.
IMO this isn't the right direction. You should disable vectorisation for
the target if it's broken instead, or workaround that with
--enable-checking=no or --enable-checking=release to not run the
self-tests.
I'd perhaps go so far as even disabling vectorization is undesirable.
This is all pointing at something broken in the port and I'd rather not
paper over it at all. It's not like big endian RISC-V is critical and
we need it limping along so bad that we need to insert this kind of hack.
So my suggestion would be the configure route or to keep such changes as
a local change rather than submitting it to the trunk. Instead Aleksa &
co should just keep fixing things and submitting the fixes to the trunk
and hopefully at some point the BE port works reliably and we'll have
the necessary infrastructure to test it going forward so that it doesn't
bitrot.
jeff
