During the work on https://github.com/rakslice/macemu/issues/36 I put in some modifications to powerpc-test.cpp to be able to generate an output file when running using CPU emulation, not just when running natively on a PowerPC system, in order to be able to compare non-JIT and JIT CPU instruction emulation.
Then I was able to track down archived from an old version of web site a copy of the previous test file for use with powerpc-test.cpp that matches the checksum referenced in the doc.
The tests in powerpc-test.cpp cover (integer) ALU, and the vector functionality in VMX / Altivec, but no FP instructions other than the floating-point stuff that is part of VMX.
I suspect that there was some other verification test suite that was available that could cover that so one didn't need to be written. Maybe I actually read a historical mention of that somewhere related to this project; I can't remember.
Anyway, as part of getting some make targets for the test ready to go upstream, maybe also get that sorted out.
Having something like test-powerpc that runs outside the scope of an entire emulated Mac would be nice, but for the purpose of just verifying that the FPU instructions have sufficient accuracy on a mostly otherwise working emulator it is not strictly essential if the other test is passing.
During the work on https://github.com/rakslice/macemu/issues/36 I put in some modifications to
powerpc-test.cppto be able to generate an output file when running using CPU emulation, not just when running natively on a PowerPC system, in order to be able to compare non-JIT and JIT CPU instruction emulation.Then I was able to track down archived from an old version of web site a copy of the previous test file for use with
powerpc-test.cppthat matches the checksum referenced in the doc.The tests in powerpc-test.cpp cover (integer) ALU, and the vector functionality in VMX / Altivec, but no FP instructions other than the floating-point stuff that is part of VMX.
I suspect that there was some other verification test suite that was available that could cover that so one didn't need to be written. Maybe I actually read a historical mention of that somewhere related to this project; I can't remember.
Anyway, as part of getting some make targets for the test ready to go upstream, maybe also get that sorted out.
Having something like
test-powerpcthat runs outside the scope of an entire emulated Mac would be nice, but for the purpose of just verifying that the FPU instructions have sufficient accuracy on a mostly otherwise working emulator it is not strictly essential if the other test is passing.