|How do I obtain a commercial license?|
|What are the run rules and allowances for CoreMark-Pro|
|How does this compare to CoreMark?|
1. Both have open score submission
2. CoreMark and CoreMark Pro perform self-verification
3. CoreMark has one integer workload with 4 functions. CoreMark Pro has 5 integer and 4 floating-point workloads.
4. CoreMark is relatively small (2k code, 16k data). CoreMark Pro is large (42k-3MB (per context)
5. CoreMark targets processor core. CoreMark Pro targets processor and memory subsystems, and provides multicore support..
|Does this replace CoreMark?|
Absolutely not. CoreMark continues to grow in popularity for analyzing microcontrollers and many embedded processors.
|What if I don't have hardware floating-point?|
You can use software floating-point emulation, but good luck - it will be slow.
|Can I optimize the code or must be it used out of the box?|
If you're not publishing CoreMark Pro results, you can do what you wish.
|What is the run-time of CoreMark-Pro?|
It might seem like the subtests are so short that the cores are able to run entirely at the burst frequency. It also might imply that you are not intending to measure workloads with sustained execution (and will therefore throttle for smartphones/tablets). However, the score of subtests is measured in iterations/s (BW) and a user may choose the number of iterations. With CoreMark Pro inside AndEBench-Pro, the iterations were set such that each workload runs for 2s on a reference device. The requirement is not on run time as such, but on the accuracy required from the timing mechanism.