A quick drive-by thought: this would disable the sanitizer on all builds, but we probably only want to disable it for release builds. The UBSan build should still check this.
A couple possibilities:
1. Gate this on some #define that we set in the build alongside array-bounds-for-release
2. Use `__builtin_assume(...)` on whatever invariant the compiler is failing to discover. `-fsanitize=builtin`, enabled by the testing UBSan build, will then check this while release builds can tell the compiler about this.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |