add 18th iteration of classifier

1 files changed, 45 insertions, 0 deletions

diff --git a/results/classifier/118/performance/1399939 b/results/classifier/118/performance/1399939
new file mode 100644
index 000000000..9fcebde4b
--- /dev/null
+++ b/results/classifier/118/performance/1399939
@@ -0,0 +1,45 @@
+performance: 0.974
+ppc: 0.912
+graphic: 0.876
+device: 0.823
+register: 0.789
+mistranslation: 0.777
+architecture: 0.773
+vnc: 0.760
+files: 0.743
+permissions: 0.729
+semantic: 0.722
+PID: 0.698
+user-level: 0.693
+TCG: 0.693
+risc-v: 0.688
+network: 0.677
+socket: 0.664
+VMM: 0.629
+debug: 0.607
+boot: 0.601
+kernel: 0.593
+arm: 0.590
+peripherals: 0.573
+hypervisor: 0.520
+i386: 0.442
+virtual: 0.421
+assembly: 0.375
+KVM: 0.371
+x86: 0.311
+
+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.
+