[Minor Feature] Install modern Clang for improved TSan and fuzzing #282
Labels
No labels
Alpha Release Requirement
Bugfix
Demo Target
Documentation
Major Feature
Minor Feature
priority:tier1-active
priority:tier2-foundation
priority:tier3-future
priority:tier4-deferred
Refactoring & Cleanup
system:animation
system:documentation
system:grid
system:input
system:performance
system:procgen
system:python-binding
system:rendering
system:ui-hierarchy
Tiny Feature
workflow:blocked
workflow:needs-benchmark
workflow:needs-documentation
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
john/McRogueFace#282
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
The build system currently uses GCC 12.2.0 (Debian 12 default). This is adequate for ASan and UBSan, but:
-fno-sanitize=function(Clang-only UBSan check), so we already have a compiler-detection workaround in CMakeLists.txtProposal
CC=clang CXX=clang++ make asanValue
--disable-gilwork-fno-sanitize=functionworks natively (no workaround needed)Related
Closing as satisfied. clang-18 is installed and was exercised as the instrumentation compiler for the #312 fuzz-coverage campaign (libFuzzer + ASan/UBSan under clang-18, with crash-corpus A/B replay). Coverage-guided fuzzing, native
-fno-sanitize=function, and Clang selection are all in place.The one remaining thread — a dedicated TSan build preset + worker-thread stress tests for free-threaded CPython — is tracked as item 6 of #336, where it belongs (it's free-threading hardening, not a toolchain install).