Am 19.08.2015 um 16:41 schrieb Artyom Tarasenko:
And if I completely disable optimizer (// #define
USE_TCG_OPTIMIZATIONS in tcg.c), it's still quite faster:
real 14m17.668s
user 14m10.241s
sys 0m6.060s
my tests also without USE_TCG_OPTIMIZATIONS
qemu 2.4.50, netbsd 6.1.5 SPARC64
without-optimization
//#define USE_TCG_OPTIMIZATIONS
pugixml compile: (without-optimization is faster)
with-optimization: ~2:51.2
without-optimization: ~2:14.1
prime.c runtime: (without-optimization is faster)
with-optimization: ~11 sec
without-optimization: ~9.9 sec
stream results (with-optimization gives better results)
with-optimization:
Your clock granularity/precision appears to be 42 microseconds.
Each test below will take on the order of 330428 microseconds.
(= 7867 clock ticks)
Function Best Rate MB/s Avg time Min time Max time
Copy: 771.5 0.214717 0.207377 0.244214
Scale: 288.1 0.573320 0.555401 0.660161
Add: 423.5 0.633523 0.566661 1.092067
Triad: 242.9 1.053032 0.987970 1.499563
without-optimization:
Your clock granularity/precision appears to be 41 microseconds.
Each test below will take on the order of 745254 microseconds.
(= 18176 clock ticks)
Function Best Rate MB/s Avg time Min time Max time
Copy: 316.6 0.524065 0.505313 0.580103
Scale: 200.5 0.813356 0.798024 0.840986
Add: 243.9 1.010247 0.984025 1.119149
Triad: 182.9 1.345601 1.312236 1.427459
