chromium-browser ver. bump
This commit is contained in:
@@ -0,0 +1,23 @@
|
||||
--- a/build/config/compiler/BUILD.gn
|
||||
+++ b/build/config/compiler/BUILD.gn
|
||||
@@ -1903,20 +1903,4 @@ config("sanitize_c_array_bounds") {
|
||||
config("sanitize_c_array_bounds") {
|
||||
if (!is_ubsan && is_clang && !(is_asan && target_cpu == "x86")) {
|
||||
- cflags = [
|
||||
- "-fsanitize=array-bounds",
|
||||
- "-fsanitize-trap=array-bounds",
|
||||
-
|
||||
- # Some code users feature detection to determine if UBSAN (or any
|
||||
- # sanitizer) is enabled, they then do expensive debug like operations. We
|
||||
- # want to suppress this behaviour since we want to keep performance costs
|
||||
- # as low as possible while having these checks.
|
||||
- "-fsanitize-ignore-for-ubsan-feature=array-bounds",
|
||||
-
|
||||
- # Because we've enabled array-bounds sanitizing we also want to suppress
|
||||
- # the related warning about "unsafe-buffer-usage-in-static-sized-array",
|
||||
- # since we know that the array bounds sanitizing will catch any out-of-
|
||||
- # bounds accesses.
|
||||
- "-Wno-unsafe-buffer-usage-in-static-sized-array",
|
||||
- ]
|
||||
}
|
||||
}
|
||||
Reference in New Issue
Block a user