On 8/5/24 4:23 PM, Mark Wielaard wrote:
Quite possibly because the damn thing claims it's "V", but in fact it's not compatible with the V1.0 spec. Sadly it's a common problem for these V0.7.1 systems.It was suggested to just ignore the machine has rvv since it isn't 1.0 compliant. So it is now configured --with-arch=rv64gc --with-abi=lp64d --with-multilib-list=lp64d but that didn't really change any of the testresults since the rvv vector tests are still all run.
Jeff