x86: 0.998
semantic: 0.995
assembly: 0.852
graphic: 0.824
i386: 0.808
architecture: 0.799
device: 0.665
ppc: 0.601
mistranslation: 0.491
boot: 0.468
vnc: 0.465
socket: 0.452
kernel: 0.422
arm: 0.353
register: 0.348
permissions: 0.325
network: 0.307
debug: 0.306
risc-v: 0.275
files: 0.203
performance: 0.197
peripherals: 0.112
PID: 0.103
virtual: 0.083
VMM: 0.082
TCG: 0.073
KVM: 0.064
hypervisor: 0.041
user-level: 0.019
--------------------
x86: 1.000
semantic: 0.988
i386: 0.987
assembly: 0.957
debug: 0.352
register: 0.270
kernel: 0.092
files: 0.049
performance: 0.045
TCG: 0.030
user-level: 0.027
virtual: 0.024
architecture: 0.015
peripherals: 0.013
device: 0.013
VMM: 0.011
PID: 0.011
hypervisor: 0.010
boot: 0.006
network: 0.006
KVM: 0.005
socket: 0.005
permissions: 0.005
graphic: 0.003
risc-v: 0.002
vnc: 0.001
mistranslation: 0.001
ppc: 0.000
arm: 0.000

x86 BLSMSK semantic bug
Description of problem:
The result of instruction BLSMSK is different with from the CPU. The value of CF is different.
Steps to reproduce:
1. Compile this code
```
void main() {
    asm("mov rax, 0x65b2e276ad27c67");
    asm("mov rbx, 0x62f34955226b2b5d");
    asm("blsmsk eax, ebx");
}
```
2. Execute and compare the result with the CPU.
    - CPU
        - CF = 0
    - QEMU
        - CF = 1
Additional information:
This bug is discovered by research conducted by KAIST SoftSec.