restructure results

1 files changed, 38 insertions, 0 deletions

diff --git a/results/classifier/zero-shot/118/debug/1795 b/results/classifier/zero-shot/118/debug/1795
new file mode 100644
index 00000000..3ea79da7
--- /dev/null
+++ b/results/classifier/zero-shot/118/debug/1795
@@ -0,0 +1,38 @@
+debug: 0.938
+ppc: 0.870
+device: 0.691
+graphic: 0.580
+performance: 0.559
+semantic: 0.323
+mistranslation: 0.305
+risc-v: 0.293
+vnc: 0.252
+network: 0.215
+architecture: 0.202
+files: 0.194
+socket: 0.150
+permissions: 0.142
+boot: 0.137
+PID: 0.121
+kernel: 0.108
+VMM: 0.094
+arm: 0.090
+peripherals: 0.086
+TCG: 0.086
+register: 0.086
+user-level: 0.078
+i386: 0.054
+hypervisor: 0.044
+virtual: 0.034
+x86: 0.027
+assembly: 0.026
+KVM: 0.024
+
+PPC: not honouring single stepping through branches and skips a nip
+Description of problem:
+When debugging in MacsBug, tracing/stepping over any branches (e.g. blt, bgt) will land on the instruction immediately passed the expected address. It appears that branches will execute the target instruction then single step to the next instruction in one go, instead of single stepping to the target instruction.
+
+For example, if a blt should land on 13371234, stepping over the branch will land on 13371238. The instruction at 13371234 still executes, but this is not the behaviour on a baremetal Mac OS system.
+Additional information:
+A <a href="https://i.imgur.com/f6dguMt.png">screenshot</a> before the branch.
+A <a href="https://imgur.com/WoVDtN7.png">screenshot<a/> after pressing 't' to step over the branch. Note that the PC is now 1E36CAB8 instead of the expected 1E36CAB4.