3 files changed, 101 insertions, 0 deletions
diff --git a/results/classifier/108/other/1611 b/results/classifier/108/other/1611
new file mode 100644
index 00000000..02a2d797
--- /dev/null
+++ b/results/classifier/108/other/1611
@@ -0,0 +1,16 @@
+device: 0.689
+graphic: 0.610
+performance: 0.514
+semantic: 0.230
+debug: 0.177
+boot: 0.097
+network: 0.069
+permissions: 0.024
+files: 0.014
+PID: 0.013
+other: 0.009
+vnc: 0.006
+socket: 0.004
+KVM: 0.002
+
+How to test rutabaga_gfx/gfxstream patches
diff --git a/results/classifier/108/other/1611394 b/results/classifier/108/other/1611394
new file mode 100644
index 00000000..ffa9753c
--- /dev/null
+++ b/results/classifier/108/other/1611394
@@ -0,0 +1,56 @@
+files: 0.742
+performance: 0.678
+device: 0.664
+socket: 0.635
+semantic: 0.634
+network: 0.607
+vnc: 0.572
+permissions: 0.567
+PID: 0.563
+other: 0.559
+debug: 0.548
+graphic: 0.473
+boot: 0.448
+KVM: 0.444
+
+qemu-ppc: Scalar Single-Precision Floating-Point instructions should not test  MSR[SPV]
+
+According to "Signal Processing Engine (SPE) Programming Environments Manual" at
+http://cache.nxp.com/files/32bit/doc/ref_manual/SPEPEM.pdf?fsrch=1&sr=1&pageNum=1
+
+c.f section 4.2.3  and also Figure 2-2.
+
+When MSR[SPV] is _NOT_ set, then the embedded scalar single-precision floating-point instructions
+should _NOT_ generate an Embedded Floating-Point Unavailable Interrupt.
+
+
+Hence, some tests for MSR[SPV] in file target-ppc/translate.c need to be removed.
+Namely, in the definitions of 
+1. GEN_SPEFPUOP_ARITH2_32_32
+2. gen_efsabs
+3. gen_efsnabs
+4. gen_efsneg
+5. GEN_SPEFPUOP_COMP_32
+
+Note, the macro GEN_SPEFPUOP_CONV_32_32 is already correct.
+
+One more thing, afaict the macro GEN_SPEFPUOP_CONV_32_64 is used by both
+efs- and efd- instructions, and will need to be split in two versions.
+The efs-use (i.e for efscfd) should be as it is today, but the use by efd-instructions 
+(e.g efdctui) will need to add a test for MSR[SPV].
+
+
+
+(I've looked at today's HEAD-revision of target-ppc/translate.c).
+
+I have filed a broader ticket, Bug #1888918, reporting a very similar issue that leads to corruption/bad arithmetic when using double-precision & vector instructions.
+
+I will be submitting a patch in the next few days that will also address this ticket.
+
+Assuming that this commit:
+https://gitlab.com/qemu-project/qemu/-/commit/8dcdb535d7cc4ba6270bb756e12e1d323254ed4e
+
+is sufficient to mark this bug as Fix Committed. Please re-open if I am mistaken.
+
+Released with QEMU v5.2.0.
+
diff --git a/results/classifier/108/other/1611979 b/results/classifier/108/other/1611979
new file mode 100644
index 00000000..bf921105
--- /dev/null
+++ b/results/classifier/108/other/1611979
@@ -0,0 +1,29 @@
+graphic: 0.871
+device: 0.782
+vnc: 0.531
+socket: 0.511
+semantic: 0.489
+debug: 0.351
+PID: 0.339
+network: 0.320
+boot: 0.310
+other: 0.161
+KVM: 0.048
+files: 0.039
+permissions: 0.012
+performance: 0.006
+
+GTK+ interface, backspace is broken in the monitor console
+
+this has been broken for over 2 years
+
+Confirmed, this is indeed broken. I sent a patch with a fix to the mailing list:
+https://marc.info/?i=1470900060-25821-1-git-send-email-thuth%40redhat.com
+
+thank you
+
+Fix has been picked up into the repository now:
+http://git.qemu.org/?p=qemu.git;a=commitdiff;h=344aa283b89bec2af9761
+
+Released with version 2.8
+