8 files changed, 764 insertions, 0 deletions
diff --git a/results/classifier/118/mistranslation-ppc/1092 b/results/classifier/118/mistranslation-ppc/1092
new file mode 100644
index 000000000..853228cbb
--- /dev/null
+++ b/results/classifier/118/mistranslation-ppc/1092
@@ -0,0 +1,74 @@
+mistranslation: 0.914
+ppc: 0.899
+device: 0.801
+graphic: 0.636
+files: 0.616
+semantic: 0.492
+network: 0.383
+i386: 0.355
+vnc: 0.339
+boot: 0.313
+socket: 0.296
+architecture: 0.217
+kernel: 0.216
+risc-v: 0.201
+PID: 0.178
+arm: 0.171
+assembly: 0.171
+user-level: 0.166
+debug: 0.164
+x86: 0.163
+TCG: 0.149
+permissions: 0.137
+performance: 0.133
+peripherals: 0.124
+register: 0.110
+virtual: 0.091
+VMM: 0.052
+hypervisor: 0.043
+KVM: 0.030
+--------------------
+ppc: 0.991
+files: 0.156
+mistranslation: 0.127
+register: 0.055
+semantic: 0.038
+assembly: 0.026
+virtual: 0.021
+debug: 0.019
+TCG: 0.015
+architecture: 0.007
+performance: 0.006
+device: 0.006
+PID: 0.005
+hypervisor: 0.005
+kernel: 0.004
+KVM: 0.003
+socket: 0.003
+peripherals: 0.002
+user-level: 0.002
+boot: 0.001
+VMM: 0.001
+network: 0.001
+risc-v: 0.001
+graphic: 0.001
+vnc: 0.000
+arm: 0.000
+permissions: 0.000
+x86: 0.000
+i386: 0.000
+
+PPC: `sraw` instructions does not set `ca` and `ca32` flags.
+Description of problem:
+The translation of Power PC instruction `sraw` and `sraw.` don't set the `ca` or `ca32` flags although, according to
+[PowerISA 3.1b](https://files.openpower.foundation/s/dAYSdGzTfW4j2r2) (page 140), they should.
+Additional information:
+This gets particular apparent if compared to `srawi` (which does set `ca`, `ca32`).
+
+**sraw**
+
+https://gitlab.com/qemu-project/qemu/-/blob/master/target/ppc/translate.c#L2914
+
+**srawi**
+
+https://gitlab.com/qemu-project/qemu/-/blob/master/target/ppc/translate.c#L2924
diff --git a/results/classifier/118/mistranslation-ppc/1655708 b/results/classifier/118/mistranslation-ppc/1655708
new file mode 100644
index 000000000..7238ef081
--- /dev/null
+++ b/results/classifier/118/mistranslation-ppc/1655708
@@ -0,0 +1,127 @@
+mistranslation: 0.960
+ppc: 0.930
+virtual: 0.918
+hypervisor: 0.836
+device: 0.812
+semantic: 0.811
+socket: 0.783
+PID: 0.745
+vnc: 0.741
+register: 0.697
+architecture: 0.673
+graphic: 0.661
+performance: 0.660
+boot: 0.654
+kernel: 0.589
+network: 0.587
+permissions: 0.583
+risc-v: 0.557
+files: 0.555
+assembly: 0.537
+arm: 0.522
+KVM: 0.520
+VMM: 0.506
+peripherals: 0.487
+TCG: 0.483
+user-level: 0.483
+debug: 0.473
+i386: 0.426
+x86: 0.424
+--------------------
+ppc: 0.929
+debug: 0.201
+semantic: 0.115
+kernel: 0.109
+x86: 0.080
+files: 0.059
+PID: 0.032
+register: 0.028
+TCG: 0.026
+virtual: 0.024
+hypervisor: 0.018
+performance: 0.016
+boot: 0.015
+device: 0.011
+user-level: 0.011
+VMM: 0.009
+socket: 0.009
+mistranslation: 0.008
+network: 0.008
+vnc: 0.005
+KVM: 0.005
+peripherals: 0.004
+architecture: 0.004
+permissions: 0.004
+assembly: 0.004
+risc-v: 0.002
+i386: 0.002
+graphic: 0.002
+arm: 0.000
+
+target/ppc/int_helper.c:2806: strange expression ?
+
+target/ppc/int_helper.c:2806:25: warning: ‘*’ in boolean context, suggest ‘&&’ instead [-Wint-in-bool-context]
+
+Source code is
+
+       zone_digit = (i * 2) ? b->u8[BCD_DIG_BYTE(i * 2)] >> 4 : zone_lead;
+
+Which I read as
+
+       zone_digit = (i * 2) ? (b->u8[BCD_DIG_BYTE(i * 2)] >> 4) : zone_lead;
+
+so I think the compiler warning is for the i * 2 lhs of the ?.
+
+I am not sure what to suggest as a bugfix.
+
+On 01/11/2017 10:41 AM, dcb wrote:
+> Public bug reported:
+> 
+> target/ppc/int_helper.c:2806:25: warning: ‘*’ in boolean context,
+> suggest ‘&&’ instead [-Wint-in-bool-context]
+> 
+> Source code is
+> 
+>        zone_digit = (i * 2) ? b->u8[BCD_DIG_BYTE(i * 2)] >> 4 :
+> zone_lead;
+
+Also, looking at BCD_DIG_BYTE():
+
+#if defined(HOST_WORDS_BIGENDIAN)
+#define BCD_DIG_BYTE(n) (15 - (n/2))
+#else
+#define BCD_DIG_BYTE(n) (n/2)
+#endif
+
+Oops. n is under-parenthesized, and will cause invalid expansions for
+some expressions.  Let's fix that as well.
+
+
+> so I think the compiler warning is for the i * 2 lhs of the ?.
+
+Yes - the compiler is complaining that 'i * 2' can only be non-zero if
+'i' was non-zero (given that the code occurs in a loop for i between 0
+and 16), so it is just as easy to write 'i ? ...' instead of the weirder
+'(i * 2) ? ...'.
+
+-- 
+Eric Blake   eblake redhat com    +1-919-301-3266
+Libvirt virtualization library http://libvirt.org
+
+
+
+> so it is just as easy to write 'i ? ...' instead of the weirder
+> '(i * 2) ? ...'.
+
+I suspect it is just possible that the i * 2 expression is a typo
+for something else, perhaps i & 2 or i << 2 or i >> 2 or something else.
+
+I don't know the code so I am unable to offer better guidance.
+ 
+
+Patch has been posted to the mailing list:
+https://lists.gnu.org/archive/html/qemu-devel/2017-01/msg02008.html
+
+Fix had been committed here:
+http://git.qemu.org/?p=qemu.git;a=commitdiff;h=365206aeb3d0bb72043d
+
diff --git a/results/classifier/118/mistranslation-ppc/1708077 b/results/classifier/118/mistranslation-ppc/1708077
new file mode 100644
index 000000000..ae8b88ddd
--- /dev/null
+++ b/results/classifier/118/mistranslation-ppc/1708077
@@ -0,0 +1,68 @@
+ppc: 0.928
+mistranslation: 0.914
+debug: 0.913
+device: 0.711
+graphic: 0.592
+PID: 0.347
+semantic: 0.277
+i386: 0.246
+vnc: 0.204
+x86: 0.176
+user-level: 0.163
+register: 0.161
+arm: 0.126
+boot: 0.123
+architecture: 0.119
+risc-v: 0.119
+socket: 0.109
+kernel: 0.106
+performance: 0.090
+network: 0.078
+VMM: 0.069
+assembly: 0.043
+peripherals: 0.042
+TCG: 0.041
+virtual: 0.035
+files: 0.026
+hypervisor: 0.006
+permissions: 0.005
+KVM: 0.004
+--------------------
+ppc: 0.997
+user-level: 0.867
+debug: 0.859
+virtual: 0.113
+TCG: 0.091
+performance: 0.034
+hypervisor: 0.026
+assembly: 0.019
+files: 0.014
+register: 0.012
+PID: 0.010
+device: 0.010
+kernel: 0.009
+network: 0.002
+semantic: 0.002
+boot: 0.002
+socket: 0.001
+graphic: 0.001
+architecture: 0.001
+peripherals: 0.001
+VMM: 0.001
+x86: 0.001
+arm: 0.001
+vnc: 0.001
+permissions: 0.000
+mistranslation: 0.000
+risc-v: 0.000
+KVM: 0.000
+i386: 0.000
+
+PPC interrupt exception！
+
+There is a exception on interrupt system when run the system with debug app on qemu-system-ppc.exe。I have try in version SHA-1: 2421f381dc38a8a6d12477c08c2f74a35a0698f8 no problem，but the next version SHA-1: 28f997a82cb509bf4775d4006b368e1bde8b7bdd have this exception。 And I found during this period in the repair of multi-threaded mutex，so I guess whether the PPC has some mutex needed are not taken into account。My english is poor，so there may be many grammatical errors。I hope you can understand the problem I described。
+
+What kind of exeception are you seeing here exactly? Can you still reproduce it with the latest version of QEMU?
+
+[Expired for QEMU because there has been no activity for 60 days.]
+
diff --git a/results/classifier/118/mistranslation-ppc/1854738 b/results/classifier/118/mistranslation-ppc/1854738
new file mode 100644
index 000000000..595f42bb6
--- /dev/null
+++ b/results/classifier/118/mistranslation-ppc/1854738
@@ -0,0 +1,104 @@
+ppc: 0.959
+mistranslation: 0.901
+user-level: 0.860
+semantic: 0.856
+files: 0.855
+architecture: 0.850
+graphic: 0.803
+peripherals: 0.801
+PID: 0.799
+performance: 0.794
+device: 0.770
+hypervisor: 0.752
+permissions: 0.741
+register: 0.719
+network: 0.671
+i386: 0.663
+assembly: 0.661
+risc-v: 0.639
+debug: 0.631
+VMM: 0.624
+kernel: 0.615
+socket: 0.611
+TCG: 0.592
+x86: 0.577
+vnc: 0.560
+KVM: 0.554
+virtual: 0.542
+arm: 0.542
+boot: 0.533
+--------------------
+ppc: 0.960
+debug: 0.392
+TCG: 0.157
+files: 0.146
+architecture: 0.132
+semantic: 0.060
+PID: 0.047
+x86: 0.040
+virtual: 0.035
+register: 0.035
+user-level: 0.033
+hypervisor: 0.032
+boot: 0.028
+socket: 0.028
+network: 0.025
+device: 0.025
+vnc: 0.022
+kernel: 0.019
+permissions: 0.015
+performance: 0.014
+peripherals: 0.013
+risc-v: 0.013
+graphic: 0.010
+arm: 0.008
+assembly: 0.004
+i386: 0.003
+VMM: 0.003
+mistranslation: 0.002
+KVM: 0.000
+
+ppc doesn't support for mttcg  but ppc64 supported
+
+Currently ppc and ppc64abi32 doesn't suppport for mttcg, I am looking for support
+```
+  ppc)
+    gdb_xml_files="power-core.xml power-fpu.xml power-altivec.xml power-spe.xml"
+  ;;
+  ppc64)
+    TARGET_BASE_ARCH=ppc
+    TARGET_ABI_DIR=ppc
+    mttcg=yes
+    gdb_xml_files="power64-core.xml power-fpu.xml power-altivec.xml power-spe.xml power-vsx.xml"
+  ;;
+  ppc64le)
+    TARGET_ARCH=ppc64
+    TARGET_BASE_ARCH=ppc
+    TARGET_ABI_DIR=ppc
+    mttcg=yes
+    gdb_xml_files="power64-core.xml power-fpu.xml power-altivec.xml power-spe.xml power-vsx.xml"
+  ;;
+  ppc64abi32)
+    TARGET_ARCH=ppc64
+    TARGET_BASE_ARCH=ppc
+    TARGET_ABI_DIR=ppc
+    echo "TARGET_ABI32=y" >> $config_target_mak
+    gdb_xml_files="power64-core.xml power-fpu.xml power-altivec.xml power-spe.xml power-vsx.xml"
+  ;;
+```
+
+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 please 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/118/mistranslation-ppc/1870911 b/results/classifier/118/mistranslation-ppc/1870911
new file mode 100644
index 000000000..dac433ea4
--- /dev/null
+++ b/results/classifier/118/mistranslation-ppc/1870911
@@ -0,0 +1,151 @@
+ppc: 0.915
+vnc: 0.877
+mistranslation: 0.874
+x86: 0.857
+semantic: 0.853
+PID: 0.849
+socket: 0.840
+user-level: 0.817
+architecture: 0.804
+arm: 0.795
+graphic: 0.794
+permissions: 0.791
+debug: 0.787
+device: 0.783
+performance: 0.776
+kernel: 0.737
+i386: 0.715
+network: 0.713
+assembly: 0.701
+risc-v: 0.700
+virtual: 0.695
+files: 0.677
+hypervisor: 0.668
+register: 0.664
+VMM: 0.657
+peripherals: 0.653
+KVM: 0.622
+boot: 0.608
+TCG: 0.545
+--------------------
+user-level: 0.920
+x86: 0.812
+risc-v: 0.800
+register: 0.466
+hypervisor: 0.281
+TCG: 0.250
+network: 0.175
+socket: 0.118
+vnc: 0.110
+virtual: 0.104
+performance: 0.092
+PID: 0.073
+files: 0.069
+boot: 0.066
+ppc: 0.047
+debug: 0.044
+device: 0.032
+semantic: 0.019
+VMM: 0.013
+permissions: 0.013
+assembly: 0.009
+i386: 0.008
+architecture: 0.004
+kernel: 0.004
+graphic: 0.003
+peripherals: 0.002
+mistranslation: 0.001
+arm: 0.001
+KVM: 0.001
+
+QEMU Crashes on Launch, Windows
+
+Hi,
+
+I an having no issues up to (and including) v5.0.0-rc0, but when I move to rc1 ... it won't even execute in Windows. If I just try to, for example, run
+
+qemu-system-x86_64.exe --version
+
+No output, it just exits. This seems to be new with this version.
+
+Thanks!
+
+On Sun, Apr 5, 2020 at 3:38 PM Russell Morris <email address hidden> wrote:
+
+> Public bug reported:
+>
+> Hi,
+>
+> I an having no issues up to (and including) v5.0.0-rc0, but when I move
+> to rc1 ... it won't even execute in Windows. If I just try to, for
+> example, run
+>
+> qemu-system-x86_64.exe --version
+>
+> No output, it just exits. This seems to be new with this version.
+>
+> Thanks!
+>
+> ** Affects: qemu
+>      Importance: Undecided
+>          Status: New
+>
+> --
+> You received this bug notification because you are a member of qemu-
+> devel-ml, which is subscribed to QEMU.
+> https://bugs.launchpad.net/bugs/1870911
+>
+> Title:
+>   QEMU Crashes on Launch, Windows
+>
+> Status in QEMU:
+>   New
+>
+> Bug description:
+>   Hi,
+>
+>   I an having no issues up to (and including) v5.0.0-rc0, but when I
+>   move to rc1 ... it won't even execute in Windows. If I just try to,
+>   for example, run
+>
+>   qemu-system-x86_64.exe --version
+>
+>   No output, it just exits. This seems to be new with this version.
+>
+>   Thanks!
+>
+> To manage notifications about this bug go to:
+> https://bugs.launchpad.net/qemu/+bug/1870911/+subscriptions
+>
+>
+
+Happens to me too with qemu-system-ppc. Earlier thread is here:
+https://lists.nongnu.org/archive/html/qemu-ppc/2020-04/msg00027.html
+
+For now compiling with --disable-pie will produce a running executable.
+
+Best,
+Howard
+
+
+Thanks for the pointer! Yep, same here - if I --disable-pie, rebuild and try again => now no crash, at least checking --version ;-).
+
+Will continue testing here, report back if I see any other oddities.
+
+Thanks again.
+
+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 please 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/118/mistranslation-ppc/1958 b/results/classifier/118/mistranslation-ppc/1958
new file mode 100644
index 000000000..f1152ad77
--- /dev/null
+++ b/results/classifier/118/mistranslation-ppc/1958
@@ -0,0 +1,81 @@
+ppc: 0.904
+mistranslation: 0.877
+graphic: 0.858
+device: 0.805
+vnc: 0.766
+files: 0.684
+semantic: 0.679
+VMM: 0.642
+architecture: 0.619
+kernel: 0.614
+PID: 0.582
+TCG: 0.569
+i386: 0.552
+register: 0.524
+socket: 0.488
+debug: 0.484
+x86: 0.481
+risc-v: 0.426
+KVM: 0.381
+peripherals: 0.377
+performance: 0.377
+arm: 0.369
+network: 0.360
+boot: 0.359
+user-level: 0.330
+assembly: 0.268
+hypervisor: 0.235
+permissions: 0.232
+virtual: 0.215
+--------------------
+ppc: 0.998
+debug: 0.552
+assembly: 0.170
+register: 0.106
+hypervisor: 0.084
+TCG: 0.053
+files: 0.036
+peripherals: 0.015
+performance: 0.012
+virtual: 0.012
+semantic: 0.011
+user-level: 0.009
+device: 0.009
+kernel: 0.007
+PID: 0.004
+architecture: 0.004
+KVM: 0.003
+VMM: 0.003
+network: 0.002
+arm: 0.002
+boot: 0.001
+x86: 0.001
+risc-v: 0.001
+permissions: 0.001
+socket: 0.001
+graphic: 0.001
+vnc: 0.001
+i386: 0.001
+mistranslation: 0.001
+
+PPC msgsnd for DOORBELL CRITICAL masked by MSR[EE] instead of MSR[CE]
+Description of problem:
+When executing PPC instruction "msgsnd r3. with r3 = 0x08000001" an DOORBELL CRITICAL exception is raised on core number 1. But this exception is masked by MSR\[EE\] bit, the MSR\[EE\] should be set to 1 in core1 to get this exception. But the NXP E500MCRM.pdf reference manual indicates that MSR\[CE\] is the mask bit for DOORBELL_CRITICAL Exception.
+Additional information:
+In qemu-8.1.2/target/ppc/excp_helper.c i try to change in ppc_next_unmasked_interrupt_generic function:
+   
+```
+if (FIELD_EX64(env->msr, MSR, CE)) {
+    /* Critical doorbell */
+    if (env->pending_interrupts & PPC_INTERRUPT_CDOORBELL) {   <- move this part from (async_deliver != 0)
+        return PPC_INTERRUPT_CDOORBELL;
+     }
+     /* External critical interrupt */
+     if (env->pending_interrupts & PPC_INTERRUPT_CEXT) {
+         return PPC_INTERRUPT_CEXT;
+     }
+}
+```
+ 
+
+And it seems to work in my case.
diff --git a/results/classifier/118/mistranslation-ppc/608107 b/results/classifier/118/mistranslation-ppc/608107
new file mode 100644
index 000000000..b776f7642
--- /dev/null
+++ b/results/classifier/118/mistranslation-ppc/608107
@@ -0,0 +1,98 @@
+ppc: 0.970
+mistranslation: 0.851
+PID: 0.819
+kernel: 0.760
+architecture: 0.746
+device: 0.708
+semantic: 0.703
+files: 0.697
+register: 0.662
+socket: 0.659
+performance: 0.647
+hypervisor: 0.603
+user-level: 0.596
+risc-v: 0.555
+network: 0.554
+vnc: 0.546
+permissions: 0.537
+assembly: 0.525
+boot: 0.515
+graphic: 0.501
+arm: 0.494
+x86: 0.432
+VMM: 0.418
+KVM: 0.395
+debug: 0.383
+peripherals: 0.382
+i386: 0.351
+TCG: 0.348
+virtual: 0.296
+--------------------
+ppc: 0.963
+architecture: 0.348
+performance: 0.092
+semantic: 0.089
+debug: 0.088
+files: 0.059
+register: 0.037
+network: 0.028
+hypervisor: 0.020
+virtual: 0.020
+PID: 0.018
+device: 0.013
+boot: 0.011
+TCG: 0.010
+socket: 0.009
+kernel: 0.008
+vnc: 0.007
+assembly: 0.006
+user-level: 0.004
+peripherals: 0.004
+risc-v: 0.004
+permissions: 0.002
+mistranslation: 0.002
+VMM: 0.002
+graphic: 0.002
+x86: 0.001
+arm: 0.001
+KVM: 0.001
+i386: 0.000
+
+ppc fails to clear MSR_POW when incurring exception
+
+QEMU VERSION: 0.12.4
+
+According to FreeScale's 'Programming Environments Manual for 32-bit Implementations of the PowerPC Architecture' [MPCFPE32B, Rev.3, 9/2005], section 6.5, table 6-7, an interrupt resets MSR_POW to zero but qemu-0.12.4 fails to do so.
+Resetting the bit is necessary in order to bring the processor out of power-management since otherwise it goes to sleep right away in the exception handler, i.e., it is impossible to leave PM-mode.
+
+
+
+Thomas Monjalon wrote:
+> From: till <email address hidden>
+>
+> According to FreeScale's 'Programming Environments Manual for 32-bit
+> Implementations of the PowerPC Architecture' [MPCFPE32B, Rev.3, 9/2005],
+> section 6.5, table 6-7, an interrupt resets MSR_POW to zero but qemu-0.12.4
+> fails to do so.
+> Resetting the bit is necessary in order to bring the processor out of power
+> management since otherwise it goes to sleep right away in the exception
+> handler, i.e., it is impossible to leave PM-mode.
+>   
+
+This doesn't look right. POW shouldn't even get stored in SRR1. Could
+you please redo the patch and make sure that mtmsr masks out MSR_POW?
+
+
+Alex
+
+
+I'm afraid I don't understand. My the problem and fix doesn't address mtmsr at all.
+It just makes sure MSR_POW is cleared in MSR when an exception occurs.
+
+Do you mean MSR_POW should masked from MSR before saving it to SRR1?
+That's already taken care of (target-ppc/helper.c:2074 [qemu-0.12.4]).
+
+As far as I can see, this problem has been fixed by this commit here:
+http://git.qemu.org/?p=qemu.git;a=commitdiff;h=41557447d30eeb944e4
+... so I'm setting the status to "Fix released" now.
+
diff --git a/results/classifier/118/mistranslation-ppc/809 b/results/classifier/118/mistranslation-ppc/809
new file mode 100644
index 000000000..d2ae7f6ed
--- /dev/null
+++ b/results/classifier/118/mistranslation-ppc/809
@@ -0,0 +1,61 @@
+ppc: 0.995
+KVM: 0.914
+mistranslation: 0.846
+device: 0.790
+performance: 0.732
+graphic: 0.543
+hypervisor: 0.478
+architecture: 0.457
+semantic: 0.453
+network: 0.349
+assembly: 0.309
+debug: 0.269
+virtual: 0.253
+arm: 0.214
+x86: 0.205
+i386: 0.191
+boot: 0.100
+peripherals: 0.088
+user-level: 0.078
+risc-v: 0.075
+kernel: 0.064
+PID: 0.051
+TCG: 0.050
+VMM: 0.038
+vnc: 0.028
+permissions: 0.021
+register: 0.020
+files: 0.013
+socket: 0.010
+--------------------
+ppc: 0.993
+kernel: 0.938
+KVM: 0.932
+assembly: 0.653
+performance: 0.368
+debug: 0.323
+virtual: 0.059
+VMM: 0.054
+semantic: 0.041
+hypervisor: 0.033
+PID: 0.029
+device: 0.026
+files: 0.019
+TCG: 0.012
+x86: 0.011
+register: 0.010
+user-level: 0.009
+mistranslation: 0.009
+architecture: 0.007
+socket: 0.007
+boot: 0.004
+permissions: 0.003
+graphic: 0.002
+i386: 0.002
+peripherals: 0.001
+risc-v: 0.001
+arm: 0.000
+network: 0.000
+vnc: 0.000
+
+ppc cpu_interrupt_exittb kvm check is inverted