rename tools/xsan.blacklist

No real way around using -fsanitize-blacklist,
but we can change the rest.

Bug: 1101491
Change-Id: I3ec84bd2911b6cf6e77eac1c9d565a398bfcde77
Reviewed-on: https://skia-review.googlesource.com/c/skia/+/305754
Reviewed-by: Mike Reed <reed@google.com>
Commit-Queue: Mike Klein <mtklein@google.com>
This commit is contained in:
Mike Klein 2020-07-24 12:16:50 -05:00 committed by Skia Commit-Bot
parent 7109434de0
commit d26b3e2d51
2 changed files with 6 additions and 6 deletions

View File

@ -260,17 +260,17 @@ config("default") {
sanitizers = "memory"
}
_blacklist = rebase_path("../tools/xsan.blacklist")
_suppressions = rebase_path("../tools/xsan.supp")
cflags += [
"-fsanitize=$sanitizers",
"-fno-sanitize-recover=$sanitizers",
"-fsanitize-blacklist=$_blacklist",
"-fsanitize-blacklist=$_suppressions",
]
if (is_win) {
cflags += [
"/FI$_blacklist",
"/FI$_suppressions",
# On Release builds, we get strange warnings about string literals.
"/GF-",
@ -280,7 +280,7 @@ config("default") {
libs += [ "$clang_win/lib/clang/$clang_win_version/lib/windows/clang_rt.asan-x86_64.lib" ]
} else {
cflags += [
"-include$_blacklist",
"-include$_suppressions",
"-fno-omit-frame-pointer",
]

View File

@ -1,7 +1,7 @@
#if 0
# This file must be a no-op C #include header, and a valid *SAN blacklist file.
# Luckily, anything starting with # is a comment to *SAN blacklist files,
# This file must be a no-op C #include header, and a valid *SAN compile-time suppression file.
# Luckily, anything starting with # is a comment to *SAN compile-time suppression files,
# and anything inside #if 0 is ignored by C. Yippee!
#
# If you want to type '*', type '.*' instead. Don't make C comments!