1 files changed, 128 insertions, 0 deletions
diff --git a/results/classifier/118/review/1902267 b/results/classifier/118/review/1902267
new file mode 100644
index 00000000..e60fa567
--- /dev/null
+++ b/results/classifier/118/review/1902267
@@ -0,0 +1,128 @@
+architecture: 0.947
+graphic: 0.900
+mistranslation: 0.896
+kernel: 0.864
+user-level: 0.858
+performance: 0.854
+hypervisor: 0.788
+device: 0.770
+ppc: 0.762
+semantic: 0.755
+network: 0.724
+register: 0.717
+debug: 0.715
+peripherals: 0.705
+assembly: 0.701
+files: 0.659
+arm: 0.646
+PID: 0.643
+socket: 0.626
+permissions: 0.616
+vnc: 0.616
+x86: 0.611
+KVM: 0.595
+virtual: 0.590
+i386: 0.573
+risc-v: 0.539
+VMM: 0.533
+TCG: 0.529
+boot: 0.480
+--------------------
+x86: 0.831
+assembly: 0.574
+debug: 0.137
+user-level: 0.090
+ppc: 0.048
+files: 0.033
+i386: 0.030
+TCG: 0.024
+arm: 0.021
+virtual: 0.019
+hypervisor: 0.014
+PID: 0.013
+semantic: 0.012
+network: 0.012
+risc-v: 0.008
+register: 0.005
+device: 0.005
+boot: 0.005
+performance: 0.004
+permissions: 0.003
+kernel: 0.003
+VMM: 0.003
+architecture: 0.003
+socket: 0.002
+vnc: 0.002
+peripherals: 0.002
+graphic: 0.001
+mistranslation: 0.001
+KVM: 0.000
+
+CPU not support 32-bit stack in 32-bit unreal mode
+
+QEMU version 5.0.0 supports 32-bit and 16-bit unreal mode. Great!
+Unfortunately, QEMU does not support 32-bit stack in unreal 32-bit mode.
+After the INT instruction, the stack is switched to 16-bit, which should not be the case. 
+At BOCHS, my code works 100%. At QEMU not works.
+
+Sample code to find out:
+
+use32
+cli
+mov ax,cs
+shl eax,16
+mov ax,NewInt80h
+mov [IDT32+4*80h],eax
+mov edx,esp
+mov esp,0x10000
+int 80h
+NewInt80h:
+xchg esp,edx
+cmp edx,0x10000-6
+jnz IsStack16Bit
+
+Stack selector loaded from GDT:
+GDT:
+real32_GDT            
+dq 0
+dw 0xFFFF,0x0000,9A00h,0xCF     ; 32-bit code descriptor
+dw 0xFFFF,0x0000,9200h,0x8F     ;   4 GB data descriptor
+dw 0xFFFF,0x0000,9A00h,0x00     ; 16-bit code descriptor
+dw 0xFFFF,0x0000,9200h,0xCF     ; 32-bit data descriptor stack
+
+
+
+
+
+The QEMU project is currently moving 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 the bug state to "Incomplete" now.
+
+If the bug has already been fixed in the latest upstream version of QEMU,
+then please close this ticket as "Fix released".
+
+If it is not fixed yet and you think that this bug report here is still
+valid, then you have two options:
+
+1) If you already have an account on gitlab.com, please open a new ticket
+for this problem in our new tracker here:
+
+    https://gitlab.com/qemu-project/qemu/-/issues
+
+and then close this ticket here on Launchpad (or let it expire auto-
+matically after 60 days). Please mention the URL of this bug ticket on
+Launchpad in the new ticket on GitLab.
+
+2) If you don't have an account on gitlab.com and don't intend to get
+one, but still would like to keep this ticket opened, then please switch
+the state back to "New" or "Confirmed" within the next 60 days (other-
+wise it will get closed as "Expired"). We will then eventually migrate
+the ticket automatically to the new system (but you won't be the reporter
+of the bug in the new system and thus you won't get notified on changes
+anymore).
+
+Thank you and sorry for the inconvenience.
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+