3 files changed, 44 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/other/1655 b/results/classifier/gemma3:12b/other/1655
new file mode 100644
index 000000000..28d50d5ff
--- /dev/null
+++ b/results/classifier/gemma3:12b/other/1655
@@ -0,0 +1,2 @@
+
+qemu-7.2.2 build failed
diff --git a/results/classifier/gemma3:12b/other/1655700 b/results/classifier/gemma3:12b/other/1655700
new file mode 100644
index 000000000..1f9b82b2c
--- /dev/null
+++ b/results/classifier/gemma3:12b/other/1655700
@@ -0,0 +1,26 @@
+
+disas/libvixl/vixl/invalset.h: possible dodgy code in binary search ?
+
+
+[qemu/disas/libvixl/vixl/invalset.h:442]: (style) Array index 'low' is used before limits check.
+
+Source code is
+
+    while (!IsValid(elements[low]) && (low < high)) ++low;
+
+Also:
+
+qemu/disas/libvixl/vixl/invalset.h:450]: (style) Array index 'middle' is used before limits check.
+
+The source code is
+
+   while (!IsValid(elements[high]) && (low < high)) --high;
+
+Mind you, these lines of code look similar but didn't get reported:
+
+    while (!IsValid(elements[middle]) && (middle < high - 1)) ++middle;
+    while (!IsValid(elements[middle]) && (low + 1 < middle)) --middle;
+
+Given that binary search is notoriously tricky to get correct and a standard C library routine
+I am puzzled as to why the standard library routine didn't get used, with of course a custom
+comparison function.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/other/1655708 b/results/classifier/gemma3:12b/other/1655708
new file mode 100644
index 000000000..0ae9c72f3
--- /dev/null
+++ b/results/classifier/gemma3:12b/other/1655708
@@ -0,0 +1,16 @@
+
+target/ppc/int_helper.c:2806: strange expression ?
+
+target/ppc/int_helper.c:2806:25: warning: ‘*’ in boolean context, suggest ‘&&’ instead [-Wint-in-bool-context]
+
+Source code is
+
+       zone_digit = (i * 2) ? b->u8[BCD_DIG_BYTE(i * 2)] >> 4 : zone_lead;
+
+Which I read as
+
+       zone_digit = (i * 2) ? (b->u8[BCD_DIG_BYTE(i * 2)] >> 4) : zone_lead;
+
+so I think the compiler warning is for the i * 2 lhs of the ?.
+
+I am not sure what to suggest as a bugfix.
\ No newline at end of file