add deepseek and gemma results

1 files changed, 21 insertions, 0 deletions

diff --git a/results/classifier/gemma3:12b/boot/1131 b/results/classifier/gemma3:12b/boot/1131
new file mode 100644
index 00000000..71f4cc1f
--- /dev/null
+++ b/results/classifier/gemma3:12b/boot/1131
@@ -0,0 +1,21 @@
+
+Multiboot: could not move values from provided mmap to another address directly.
+Description of problem:
+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;
+```
+Steps to 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 information:
+#