1 files changed, 65 insertions, 0 deletions
diff --git a/results/classifier/108/other/1780814 b/results/classifier/108/other/1780814
new file mode 100644
index 00000000..4f56d58a
--- /dev/null
+++ b/results/classifier/108/other/1780814
@@ -0,0 +1,65 @@
+graphic: 0.759
+device: 0.740
+PID: 0.605
+other: 0.592
+semantic: 0.555
+network: 0.533
+permissions: 0.475
+debug: 0.465
+files: 0.456
+socket: 0.439
+performance: 0.411
+vnc: 0.383
+boot: 0.381
+KVM: 0.220
+
+lib/raid6/neon4.c:118:1: internal compiler error
+
+I am facing below issue when i am trying to cross compile kernel for raspberry pi 3.
+please give solution .
+
+
+Below is log
+
+
+
+CHK     include/config/kernel.release
+  CHK     include/generated/uapi/linux/version.h
+  CHK     include/generated/utsrelease.h
+  CHK     include/generated/bounds.h
+  CHK     include/generated/timeconst.h
+  CHK     include/generated/asm-offsets.h
+  CALL    scripts/checksyscalls.sh
+  CHK     scripts/mod/devicetable-offsets.h
+  CHK     include/generated/compile.h
+  CHK     kernel/config_data.h
+  CC [M]  lib/raid6/neon4.o
+lib/raid6/neon4.c: In function ‘raid6_neon4_gen_syndrome_real’:
+lib/raid6/neon4.c:118:1: internal compiler error: in dwarf2out_frame_debug_adjust_cfa, at dwarf2cfi.c:1078
+ }
+ ^
+Please submit a full bug report,
+with preprocessed source if appropriate.
+See <https://bugs.launchpad.net/gcc-linaro> for instructions.
+scripts/Makefile.build:328: recipe for target 'lib/raid6/neon4.o' failed
+make[2]: *** [lib/raid6/neon4.o] Error 1
+scripts/Makefile.build:587: recipe for target 'lib/raid6' failed
+make[1]: *** [lib/raid6] Error 2
+Makefile:1034: recipe for target 'lib' failed
+
+Hi -- this is an internal compiler error reported by your compiler. It's not a QEMU bug. The message suggests that you report it as a GCC bug: "See <https://bugs.launchpad.net/gcc-linaro> for instructions".
+
+
+Thanks peter maydell for your comments.
+
+
+
+Hi Peter Maydell ,
+
+is that GCC compiler error or cross-compiler error ?
+
+It must be the cross compiler. (Why did you report this against QEMU anyway?)
+
+
+I thought it was QEMU issue. Sorry for that.
+