==25613== Your program just tried to execute an instruction that Valgrind
==25613== did not recognise. There are two possible reasons for this.
==25613== 2. The instruction is legitimate but Valgrind doesn't handle it,
==25613== i.e. it's Valgrind's fault. If you think this is the case or
==25613== you are not sure, please let us know and we'll try to fix it.
Valgrind doesn’t implement support for your fancy new CPU yet.
In the meantime, you can work around it by asking Zig to target an older CPU profile, for example -target x86_64-linux -mcpu=x86_64_v3.