4 files changed, 147 insertions, 0 deletions
diff --git a/results/classifier/118/device/184 b/results/classifier/118/device/184
new file mode 100644
index 00000000..601e46fe
--- /dev/null
+++ b/results/classifier/118/device/184
@@ -0,0 +1,31 @@
+architecture: 0.991
+device: 0.964
+performance: 0.894
+graphic: 0.742
+arm: 0.629
+network: 0.610
+assembly: 0.536
+boot: 0.502
+risc-v: 0.463
+kernel: 0.365
+x86: 0.298
+i386: 0.291
+debug: 0.289
+semantic: 0.263
+ppc: 0.226
+hypervisor: 0.185
+peripherals: 0.160
+socket: 0.135
+KVM: 0.135
+VMM: 0.124
+PID: 0.119
+register: 0.114
+permissions: 0.106
+vnc: 0.103
+mistranslation: 0.099
+virtual: 0.069
+user-level: 0.060
+TCG: 0.041
+files: 0.040
+
+SSE CMP ops with 8bit immediate throw sigill with oversized byte
diff --git a/results/classifier/118/device/1843 b/results/classifier/118/device/1843
new file mode 100644
index 00000000..54fc78af
--- /dev/null
+++ b/results/classifier/118/device/1843
@@ -0,0 +1,45 @@
+device: 0.883
+graphic: 0.667
+performance: 0.433
+debug: 0.428
+PID: 0.372
+semantic: 0.332
+mistranslation: 0.247
+peripherals: 0.189
+arm: 0.184
+boot: 0.146
+socket: 0.144
+network: 0.092
+virtual: 0.091
+user-level: 0.085
+kernel: 0.084
+risc-v: 0.083
+assembly: 0.080
+permissions: 0.075
+hypervisor: 0.062
+register: 0.060
+vnc: 0.060
+TCG: 0.050
+i386: 0.048
+ppc: 0.042
+files: 0.040
+VMM: 0.037
+architecture: 0.037
+x86: 0.022
+KVM: 0.007
+
+Multitouch - GTK:  Tapping 3 points or more at too close in interval causes all points to be lost
+Description of problem:
+When using the new multitouch input device, if you use three or more fingers within two rapid interval, the all finger inputs get dropped.
+Steps to reproduce:
+ANDROID
+1. Download and install BlissOS
+2. Swipe with two fingers
+3. try multitouch debug app
+
+FEDORA
+1. Load fedora
+2. install wev
+3. try touch 3 or more points
+Additional information:
+Not sure what logs are relevant
diff --git a/results/classifier/118/device/1844644 b/results/classifier/118/device/1844644
new file mode 100644
index 00000000..66970a4b
--- /dev/null
+++ b/results/classifier/118/device/1844644
@@ -0,0 +1,40 @@
+device: 0.888
+network: 0.724
+socket: 0.664
+architecture: 0.638
+graphic: 0.554
+peripherals: 0.475
+files: 0.440
+arm: 0.376
+kernel: 0.374
+semantic: 0.311
+performance: 0.297
+boot: 0.283
+permissions: 0.262
+risc-v: 0.234
+hypervisor: 0.213
+vnc: 0.213
+user-level: 0.185
+register: 0.147
+virtual: 0.141
+debug: 0.139
+ppc: 0.136
+PID: 0.115
+x86: 0.105
+i386: 0.098
+VMM: 0.082
+mistranslation: 0.079
+assembly: 0.066
+TCG: 0.030
+KVM: 0.015
+
+Compiler warnings using MSVC
+
+The following line of code results in an implicit truncation of an uint16_t value to an uint8_t variable, which triggers a compiler warning in MSVC : https://github.com/qemu/qemu/blob/f8c3db33a5e863291182f8862ddf81618a7c6194/hw/usb/dev-hub.c#L387
+(Two lines down, the same thing happens.)
+
+This warning can be silenced by doing an explicit truncation, for example by a casting the value explicitly to uint8_t type, or by anding the value with 0xFF.
+
+Hi; MSVC is not a supported compiler for QEMU. We expect it to be built with either gcc or llvm.
+
+
diff --git a/results/classifier/118/device/1847 b/results/classifier/118/device/1847
new file mode 100644
index 00000000..0b87d6b2
--- /dev/null
+++ b/results/classifier/118/device/1847
@@ -0,0 +1,31 @@
+device: 0.924
+architecture: 0.858
+network: 0.675
+mistranslation: 0.555
+performance: 0.496
+arm: 0.491
+graphic: 0.358
+debug: 0.344
+boot: 0.304
+semantic: 0.297
+peripherals: 0.179
+assembly: 0.175
+hypervisor: 0.160
+ppc: 0.143
+virtual: 0.136
+kernel: 0.075
+user-level: 0.058
+i386: 0.058
+PID: 0.058
+risc-v: 0.058
+files: 0.050
+register: 0.046
+permissions: 0.042
+socket: 0.030
+VMM: 0.020
+TCG: 0.017
+vnc: 0.017
+x86: 0.013
+KVM: 0.003
+
+TriCore missing ftoq31, ftoq31z, and q31tof instructions