Sanitizers enabled default environments - #53
Conversation
…entation of libc++
Factored out sanitizers options and removed ignorelist selection from toolchain, this is a project matter.
…generator (i.e. handle hfc target scan which uses Makefile by mistake)
…es from Docker Layers
…elease) Required adding compression support to LLVM, so that the splitted debug symbol could be generated with compression.
daminetreg
changed the title
pysco68
left a comment
pysco68
left a comment
There was a problem hiding this comment.
LGTM except for that hardcoded install version. I'm wondering if we can/could make use of multi-stage dockerfiles to have a lighter-weight result by separating the LLVM build out into a builder stage (just food for thoughts)
…R_BUILD_ADDITIONAL_PARAMETERS: "--build-context tipi..."
In general I agree but this image is tested and running and I don't want to modify to much in this scope, in general as follow-up work if there is demand for the image I agree to invest in improving. We could model it on the musl image which does that well, however this would require an expensive retest at this stage. |
Also it seems that despite multi-stage build of the musl clang, that environment is faster to build than the musl libc environment : |
2 participants
This introduces a cmake-re environment with clang20 that can be used for C++20 compilation or for MSAN instrumentation
It provides an environment that has multiple CMAKE_TOOLCHAIN_FILE that enables uses of the MSAN instrumentation on the complete stack, by also providing an instrumented libc++.
📂 Example : https://github.com/tipi-build/example-cmake-re-sanitizers
📹 Explanatory Video : Instrumenting the Stack: Strategies for End-to-end Sanitizer Adoption - Damien Buhl - CppCon 2025