5 files changed, 228 insertions, 0 deletions
diff --git a/results/classifier/108/other/1780 b/results/classifier/108/other/1780
new file mode 100644
index 000000000..53d798e27
--- /dev/null
+++ b/results/classifier/108/other/1780
@@ -0,0 +1,32 @@
+graphic: 0.882
+device: 0.724
+network: 0.589
+semantic: 0.561
+vnc: 0.436
+debug: 0.427
+boot: 0.398
+performance: 0.395
+PID: 0.393
+socket: 0.311
+permissions: 0.230
+files: 0.097
+other: 0.041
+KVM: 0.040
+
+PowerPC mishandles xscmpudp instruction
+Description of problem:
+xscmpudp instruction is mishandled
+Steps to reproduce:
+1. Compile the attached program with VSX (e.g. `RUSTFLAGS=-Ctarget-feature=+vsx cargo build --target=powerpc64-unknown-linux-gnu`)
+2. Run the program and expect assertions to pass.
+3. See assertions fail.
+Additional information:
+When VSX is disabled, the `fcmpu` instruction is emitted instead (and handled properly).  See the offending program:
+```
+pub fn main() {
+    use std::hint::black_box;
+    assert!(black_box(f64::NAN)
+        .clamp(black_box(0f64), black_box(0f64))
+        .is_nan());
+}
+```
diff --git a/results/classifier/108/other/1780812 b/results/classifier/108/other/1780812
new file mode 100644
index 000000000..1fe8cb460
--- /dev/null
+++ b/results/classifier/108/other/1780812
@@ -0,0 +1,31 @@
+semantic: 0.850
+graphic: 0.838
+device: 0.831
+network: 0.722
+socket: 0.701
+performance: 0.653
+PID: 0.628
+other: 0.627
+permissions: 0.616
+debug: 0.606
+files: 0.591
+vnc: 0.565
+boot: 0.541
+KVM: 0.286
+
+Full-Screen Switch Does Nothing When Using SDL
+
+When using SDL switches, e.g.
+
+-sdl -full-screen -display sdl
+
+... you'd expect the display to start full-screen, as per the switch description, but it just starts in a window. Pressing the full-screen key combination (Ctrl+Alt+F) enters fullscreen mode as expected.
+
+Tested on QEmu 2.12.0 using qemu-system-x86_64.
+
+Suggested a patch here:
+http://marc.info/?<email address hidden>
+
+Fix has been merged:
+https://git.qemu.org/?p=qemu.git;a=commitdiff;h=6fb34ffcaae0823
+
diff --git a/results/classifier/108/other/1780814 b/results/classifier/108/other/1780814
new file mode 100644
index 000000000..4f56d58a2
--- /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.
+
diff --git a/results/classifier/108/other/1780815 b/results/classifier/108/other/1780815
new file mode 100644
index 000000000..ffb1617ef
--- /dev/null
+++ b/results/classifier/108/other/1780815
@@ -0,0 +1,28 @@
+device: 0.803
+graphic: 0.751
+performance: 0.659
+PID: 0.636
+semantic: 0.609
+network: 0.600
+other: 0.596
+vnc: 0.578
+files: 0.567
+socket: 0.555
+permissions: 0.507
+debug: 0.440
+boot: 0.428
+KVM: 0.285
+
+SDL Doesn't Rescale Image on Resolution Change
+
+Whilst in fullscreen mode, if the guest changes resolution for whatever reason, the screen doesn't update the scaling so you end up looking at only part of the screen, e.g. if the guest changes from 640x480 to 1024x768, the image will still be fullscreen, but what you're actually looking at will be the top-left most 640x480 segment of the screen stretched out.
+
+Manually going out of fullscreen mode and then back in fixes the scaling, but you have to do that every time the guest changes resolution.
+
+QEmu 2.12.0 using qemu-system-x86_64 with Arch Linux host.
+
+The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now.
+If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Or mark it as "Fix Released" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience.
+
+[Expired for QEMU because there has been no activity for 60 days.]
+
diff --git a/results/classifier/108/other/1780928 b/results/classifier/108/other/1780928
new file mode 100644
index 000000000..39a05667f
--- /dev/null
+++ b/results/classifier/108/other/1780928
@@ -0,0 +1,72 @@
+debug: 0.885
+permissions: 0.877
+other: 0.867
+semantic: 0.862
+graphic: 0.847
+performance: 0.827
+PID: 0.824
+network: 0.815
+files: 0.815
+device: 0.805
+socket: 0.768
+boot: 0.750
+KVM: 0.686
+vnc: 0.657
+
+v2.12.0-2321-gb34181056c: vcpu hotplug crashes qemu-kvm with segfault
+
+vcpu hotplug crashes upstream qemu(v2.12.0-2321-gb34181056c), vcpu hotplug works fine in v2.12.0-rc4.
+
+Host: Power8, kernel: 4.18.0-rc2-00037-g6f0d349d922b
+Guest: Power8, kernel: 4.18.0-rc3-00183-gc42c12a90545 (base image: fedora27 ppc64le)
+
+/usr/share/avocado-plugins-vt/build/qemu/ppc64-softmmu/qemu-system-ppc64 -M pseries,accel=kvm,max-cpu-compat=power8 -m 8192 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x2 -drive file=/var/lib/avocado/data/avocado-vt/images/jeos-27-ppc64le.qcow2,format=qcow2,if=none,id=drive1 -device scsi-hd,drive=drive1,bus=scsi0.0 -smp 1,cores=1,threads=1,sockets=1,maxcpus=8 -serial /dev/pts/0 -monitor stdio -vga none -nographic -kernel /home/kvmci/linux/vmlinux -append 'root=/dev/sda2 rw console=tty0 console=ttyS0,115200 init=/sbin/init initcall_debug' -nic user,model=virtio-net-pci 
+QEMU 2.12.50 monitor - type 'help' for more information
+(qemu) device_add host-spapr-cpu-core,id=core1,core-id=1
+Segmentation fault (core dumped)
+
+
+Guest initial cpu:
+# lscpu
+Architecture:        ppc64le
+Byte Order:          Little Endian
+CPU(s):              1
+On-line CPU(s) list: 0
+Thread(s) per core:  1
+Core(s) per socket:  1
+Socket(s):           1
+NUMA node(s):        1
+Model:               2.1 (pvr 004b 0201)
+Model name:          POWER8 (architected), altivec supported
+Hypervisor vendor:   KVM
+Virtualization type: para
+L1d cache:           64K
+L1i cache:           32K
+NUMA node0 CPU(s):   0
+
+Reverting the below comment makes CPU hotplug work again:
+
+commit a028dd423ee6dfd091a8c63028240832bf10f671
+
+    ppc/xics: introduce ICP DeviceRealize and DeviceReset handlers
+    
+    This changes the ICP realize and reset handlers in DeviceRealize and
+    DeviceReset handlers. parent handlers are now called from the
+    inheriting classes which is a cleaner object pattern.
+   
+
+
+The parent class (ie, TYPE_ICP) doesn't implement DeviceClass::reset(). It directly registers a reset handler with qemu_register_reset() instead. This is needed for cold plugged ICPs to be reset during machine reset since they're not SysBus devices.
+
+Cedric's patch missed that, but rather than reverting it, I'd rather go forward and:
+- introduce an abstract TYPE_ICP_BASE class that implements DeviceClass::reset()
+- have the current TYPE_ICP and all other specialized ICP types to derive from TYPE_ICP_BASE
+- have all specialized ICP types to register reset handlers with qemu_register_reset()
+
+This would match what was recently done with the ICS types.
+
+
+Fixed by:
+
+https://git.qemu.org/?p=qemu.git;a=commitdiff;h=b585395b655a6c1f9d9ebf1f0890e76d0708eed6
+