Issues - conflict-set - Weaselab

weaselab/conflict-set

Labels Milestones New Issue

Run MSAN in CI for arm

by andrew was closed 2026-08-03 12:27:51 +00:00

We write it in assembly because it's not UB in assembly. Not because MSAN doesn't track it.

by andrew was closed 2026-08-03 04:59:28 +00:00

ARM NEON scan helpers truncate 64-bit versions when USE_64_BIT=1, producing false conflicts

by weaselbot was closed 2026-08-03 12:26:09 +00:00

aarch64 Node16 SIMD helpers load uninitialized child slots

by weaselbot was closed 2026-08-03 13:42:51 +00:00

skip_list: addWrites passes null pointers to memcmp (undefined behavior) on every call

by weaselbot was closed 2026-07-13 21:55:54 +00:00

hash_table implementation returns -1 from getBytes(), violating the API contract

by weaselbot was closed 2026-07-08 13:58:48 +00:00

strinc() and prefixRange() invoke undefined behavior on empty input

by weaselbot was closed 2026-06-29 18:26:05 +00:00

RealDataBench.cpp reads past line bounds and passes invalid versions

by weaselbot was closed 2026-06-29 18:50:00 +00:00

Move-assignment operator leaks the old ConflictSet::impl and mishandles self-assignment

by weaselbot was closed 2026-06-22 18:40:27 +00:00

test_update_zero_should_commit / test_update_zero_should_conflict omit result assertions

by weaselbot was closed 2026-06-22 19:29:56 +00:00

ConflictSet is implicitly copyable in C++98/C++03, causing double-free

by weaselbot was closed 2026-06-22 23:45:01 +00:00

CMake Unix Makefiles generator has a parallel build race for conflict-set.o

by weaselbot was closed 2026-06-22 19:08:10 +00:00

Python wrapper declares void-returning C functions with default c_int restype

by weaselbot was closed 2026-06-22 01:12:59 +00:00