Re: nOpcodesPerTimeslice Safety Issues
DOH! Haha, that may be useful
The code will run each benchmark 30 times on the Opcode setting you choose in the source code.
The output is a CSV file output format which you just save into a CSV file using windows notepad.
On the PC-Emulator the benchmarks are quick but on the Cortex they may take longer, I estimated
that it takes roughly an hour to wait for the benchmarks to finish and push the data into a file.