* ConflictSet.cpp: enable the interleaved read/write path whenever
musttail is available, falling back to the default calling convention
when preserve_none is not supported. This prevents a large block of
compiled-but-dead code from being counted in coverage.
* CMakeLists.txt: detect which arch-specific hardening-check options the
installed hardening-check binary supports, including the newer
hyphenated spellings, so the release test no longer fails with an
unknown option.
* .gitea/workflows/ci.yml: build the coverage job with
-DUSE_SIMD_FALLBACK=ON so AVX512-only functions that cannot execute on
the CI runners are not counted against line coverage.
The custom command that links conflict-set.o depends on
$<TARGET_OBJECTS:conflict-set-object>, but that generator expression
does not create a target-level dependency. With the Unix Makefiles
generator, parallel builds can start building the consuming libraries
before the object library's build rule is available, producing:
gmake[3]: *** No rule to make target
'CMakeFiles/conflict-set-object.dir/ConflictSet.cpp.o', needed by
'conflict-set.o'. Stop.
Add add_dependencies() so that conflict-set and conflict-set-static
cannot build until conflict-set-object has produced its object files.
Closes#47
weaselbot
