diff options
Diffstat (limited to 'ollama/preambel')
| -rw-r--r-- | ollama/preambel | 62 |
1 files changed, 0 insertions, 62 deletions
diff --git a/ollama/preambel b/ollama/preambel deleted file mode 100644 index d2d498f28..000000000 --- a/ollama/preambel +++ /dev/null @@ -1,62 +0,0 @@ -We have this gitlab issue for the project qemu. This is a semantic mistranslation bug: ----- -x86 BLSMSK semantic bug -Host environment - -Operating system: Windows 10 20H2 -OS/kernel version: WSL2 Ubuntu 20.04.4 LTS (GNU/Linux 5.10.102.1-microsoft-standard-WSL2 x86_64) -Architecture: x86 -QEMU flavor: qemu-x86_64 -QEMU version: 7.1.90 (v7.2.0-rc0) -QEMU command line: qemu-x86_64 -cpu max a.out - -Emulated/Virtualized environment - -Operating system: None -OS/kernel version: None -Architecture: x86 - -Description of problem -The result of instruction BLSMSK is different with from the CPU. The value of CF is different. - -Steps to reproduce - -Compile this code - -void main() { - asm("mov rax, 0x65b2e276ad27c67"); - asm("mov rbx, 0x62f34955226b2b5d"); - asm("blsmsk eax, ebx"); -} - -Execute and compare the result with the CPU. -CPU CF = 0 -QEMU CF = 1 ----- - -This issue results in the following toml: ----- -id = 1371 -title = "x86 BLSMSK semantic bug" -state = "closed" -created_at = "2022-12-16T06:43:29.794Z" -closed_at = "2023-03-01T01:08:38.844Z" -url = "https://gitlab.com/qemu-project/qemu/-/issues/1371" -host-os = "Windows 10 20H2" -host-arch = "x86" -qemu-version = "7.1.90 (v7.2.0-rc0)" -guest-os = "None" -guest-arch = "x86" -description = """The result of instruction BLSMSK is different with from the CPU. The value of CF is different.""" -reproducer = """ -void main() { - asm("mov rax, 0x65b2e276ad27c67"); - asm("mov rbx, 0x62f34955226b2b5d"); - asm("blsmsk eax, ebx"); -} -""" -additional = """This bug is discovered by research conducted by KAIST SoftSec.""" -semantic = "yes" ----- - -For the following mailing thread, output only a toml with the corresponding variables. If an information cannot be gathered, put "n/a" instead. But you have to determine, if it is a semantic bug or not: |