From 9260319e7411ff8281700a532caa436f40120ec4 Mon Sep 17 00:00:00 2001 From: Christian Krinitsin Date: Fri, 30 May 2025 16:52:07 +0200 Subject: gitlab scraper: download in toml and text format --- .../host_missing/accel_missing/1131.toml | 28 ---------------------- 1 file changed, 28 deletions(-) delete mode 100644 gitlab/issues/target_i386/host_missing/accel_missing/1131.toml (limited to 'gitlab/issues/target_i386/host_missing/accel_missing/1131.toml') diff --git a/gitlab/issues/target_i386/host_missing/accel_missing/1131.toml b/gitlab/issues/target_i386/host_missing/accel_missing/1131.toml deleted file mode 100644 index caa0131c..00000000 --- a/gitlab/issues/target_i386/host_missing/accel_missing/1131.toml +++ /dev/null @@ -1,28 +0,0 @@ -id = 1131 -title = "Multiboot: could not move values from provided mmap to another address directly." -state = "closed" -created_at = "2022-07-30T14:42:03.649Z" -closed_at = "2022-08-17T07:25:08.613Z" -labels = ["target: i386"] -url = "https://gitlab.com/qemu-project/qemu/-/issues/1131" -host-os = "Windows 11 with MSYS" -host-arch = "x86_64" -qemu-version = "master branch(fc2cc19ffa02c86ec1471ec8fdbc39d33fcec626)" -guest-os = "n/a" -guest-arch = "n/a" -description = """When using `-kernel` to load a Multiboot file which requires a memory map(MULTIBOOT_MEMORY_INFO flag) and trying to move the values in the provided mmap entries to another address directly, QEMU reboots. -```c -xxx = mmap->addr; -``` - -When moving with volatile, everything works well: -```c -volatile unsigned long long addr = mmap->addr; -xxx = addr; -```""" -reproduce = """1. Source code here: [github/xtexChooser/toop/boot/multiboot/src/multiboot.c](https://github.com/xtexChooser/toop/blob/51153319d4f2320ae9a9277ffffad3f67a335fe9/boot/multiboot/src/multiboot.c#L32) -2. Minimized reproduce: [gist.github.com/xtexChooser/22017d662c8144b7abcb0b18c2afb09c](https://gist.github.com/xtexChooser/22017d662c8144b7abcb0b18c2afb09c) -3. I am sure that 0x00001210 is writable, it is empty in the memory map and QEMU works correctly when writing a zero value to here. -4. The reproducer is available without any module, when it works, it should keep running without any output, if QEMU reboots, the screen should flash as it clears and prints the BIOS information again. -5. If move with volatile(as the `multiboot_works.c` in reproducer), the reproducer works correctly.""" -additional = """#""" -- cgit v1.2.3