summary refs log tree commit diff stats
path: root/results/classifier/108/performance/1399939
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/108/performance/1399939')
-rw-r--r--results/classifier/108/performance/139993930
1 files changed, 30 insertions, 0 deletions
diff --git a/results/classifier/108/performance/1399939 b/results/classifier/108/performance/1399939
new file mode 100644
index 000000000..47e28ea22
--- /dev/null
+++ b/results/classifier/108/performance/1399939
@@ -0,0 +1,30 @@
+performance: 0.974
+graphic: 0.876
+device: 0.823
+vnc: 0.760
+other: 0.757
+files: 0.743
+permissions: 0.729
+semantic: 0.722
+PID: 0.698
+network: 0.677
+socket: 0.664
+debug: 0.607
+boot: 0.601
+KVM: 0.371
+
+Qemu build with -faltivec and maltivec support  in 
+
+if is possible add the build support for qemu for have the  -faltivec -maltivec in CPPFLAGS  for make the emulation more faster on PPC equiped machine . 
+Thank you
+
+We assume that your C compiler generates decently optimised code that uses the features of your host CPU with just the standard -O2 optimisation flag. If this isn't the case, you can use configure's --extra-cflags argument (eg "--extra-cflags=-faltivec -maltivec") to get the build process to pass arbitrary flags to the compiler. Is that not sufficient here?
+
+
+Will check it , i had been made my personal build modding the Makefile with altivec commands in CPPFLAGS.
+i dont know if it was a placebo effect but look like everything is more faster.
+
+
+
+Closing this ticket since adding CPPFLAGS to configure is possible.
+