3 files changed, 76 insertions, 0 deletions

diff --git a/gitlab/issues/target_arm/host_x86/accel_TCG/1581.toml b/gitlab/issues/target_arm/host_x86/accel_TCG/1581.toml
new file mode 100644
index 000000000..05ded13b9
--- /dev/null
+++ b/gitlab/issues/target_arm/host_x86/accel_TCG/1581.toml
@@ -0,0 +1,22 @@
+id = 1581
+title = "QEMU TCG crashes when running on windows"
+state = "closed"
+created_at = "2023-04-06T02:34:59.134Z"
+closed_at = "2023-04-11T09:20:30.558Z"
+labels = ["Closed::Fixed", "accel: TCG", "host: x86", "hostos: Windows", "kind::Bug", "target: arm"]
+url = "https://gitlab.com/qemu-project/qemu/-/issues/1581"
+host-os = "Windows 10 22H2"
+host-arch = "x86"
+qemu-version = "v8.0.0-rc2"
+guest-os = "linux buildroot"
+guest-arch = "arm64"
+description = """QEMU crashes immediately after startup and shows an assertion failure：
+
+ERROR:C:/msys64/home/xxx/qemu/tcg/i386/tcg-target.c.inc:1085:tcg_out_addi_ptr: assertion failed: (64 == 32)
+
+Bail out! ERROR:C:/msys64/home/xxx/qemu/tcg/i386/tcg-target.c.inc:1085:tcg_out_addi_ptr: assertion failed: (64 ==
+ 32)"""
+reproduce = """NA"""
+additional = """1. This problem only occurs when the host system is windows, and the same QEMU configuration does not have this problem when the host system is Linux.
+2. This problem is related to the -smp parameter of QEMU. If the smp parameter is 1, this problem will not occur.
+3. This problem does not exist in the QEMU version 7.2."""
diff --git a/gitlab/issues/target_arm/host_x86/accel_TCG/1592.toml b/gitlab/issues/target_arm/host_x86/accel_TCG/1592.toml
new file mode 100644
index 000000000..ce2d0c431
--- /dev/null
+++ b/gitlab/issues/target_arm/host_x86/accel_TCG/1592.toml
@@ -0,0 +1,24 @@
+id = 1592
+title = "QEMU v8.0.0 crashes when running in TCG mode on windows OS"
+state = "closed"
+created_at = "2023-04-12T01:40:09.942Z"
+closed_at = "2023-05-17T06:20:02.268Z"
+labels = ["Closed::Fixed", "accel: TCG", "host: x86", "hostos: Windows", "target: arm"]
+url = "https://gitlab.com/qemu-project/qemu/-/issues/1592"
+host-os = "Windows 10 22H2"
+host-arch = "x86_64"
+qemu-version = "v8.0.0"
+guest-os = "linux buildroot"
+guest-arch = "arm64"
+description = """This bug is a follow-up to issue #1581. 
+After the patch 7d9e1ee424b06a43708be02474e6714962cfee92 is merged, QEMU segfaults at startup.
+And the location where the segfault occurs here(from coredump):
+```
+atomic_common.c.inc:60
+CMPXCHG_HELPER(cmpxchgo_le, Int128)
+```"""
+reproduce = """NA"""
+additional = """1. This problem only occurs when the host system is windows, and the same QEMU configuration does not have this problem when the host system is Linux.
+2. This problem is related to the -smp parameter of QEMU. If the smp parameter is 1, this problem will not occur.
+3. This problem does not exist in the QEMU version 7.2.
+4. What is even more confusing is that if you use gdb to load qemu and run it, this issue cannot be reproduced."""
diff --git a/gitlab/issues/target_arm/host_x86/accel_TCG/1642.toml b/gitlab/issues/target_arm/host_x86/accel_TCG/1642.toml
new file mode 100644
index 000000000..6b6010e76
--- /dev/null
+++ b/gitlab/issues/target_arm/host_x86/accel_TCG/1642.toml
@@ -0,0 +1,30 @@
+id = 1642
+title = "Qemu aarch64 tcg crashes when emulating an STXP instruction but only on a Windows host"
+state = "closed"
+created_at = "2023-05-10T16:55:29.637Z"
+closed_at = "2023-05-17T06:20:02.276Z"
+labels = ["Closed::Fixed", "accel: TCG", "host: x86", "hostos: Windows", "kind::Bug", "target: arm"]
+url = "https://gitlab.com/qemu-project/qemu/-/issues/1642"
+host-os = "Windows 10 22H2"
+host-arch = "x86"
+qemu-version = "8.0.0"
+guest-os = "Windows Server 2022"
+guest-arch = "arm64"
+description = """Qemu segfaults when trying to emulate an STXP instruction, but only when running natively on a windows host (msys2 build). This is not the same as https://gitlab.com/qemu-project/qemu/-/issues/1581.
+
+I've managed to git-bisect it to this change: https://github.com/qemu/qemu/commit/546789c7df8866c55cae8d3195e8e58328a35d51
+Sadly i cannot investigate it further and contribute a fix, but it seems like a problem with one of the I128 arguments to `helper_atomic_cmpxchgo_le `
+
+UPD: Issue is also in master (as of `caa9cbd566877b34e9abcc04d936116fc5e0ab28`)"""
+reproduce = """N/A"""
+additional = """```
+Thread 9 received signal SIGSEGV, Segmentation fault.
+0x00007ff67efc32dc in helper_atomic_cmpxchgo_le (env=0x24796b08c10, addr=18446684150325987376, oldv=46236672343829145701101521005152, newv=2595395441251766838621186119693696, oi=3650) at ../accel/tcg/atomic_common.c.inc:60
+60      CMPXCHG_HELPER(cmpxchgo_le, Int128)
+(gdb) bt
+#0  0x00007ff67efc32dc in helper_atomic_cmpxchgo_le (env=0x24796b08c10,
+    addr=18446684150325987376, oldv=46236672343829145701101521005152,
+    newv=2595395441251766838621186119693696, oi=3650) at ../accel/tcg/atomic_common.c.inc:60
+#1  0x00000247a124f73d in ?? ()
+
+```"""