diff options
author | David Benjamin <davidben@chromium.org> | 2019-06-19 17:59:05 -0400 |
---|---|---|
committer | David Benjamin <davidben@chromium.org> | 2019-06-19 17:59:05 -0400 |
commit | f564874f49556d930882645a348fcd6ddc6847b0 (patch) | |
tree | 4d9d3f5dc1cd06357b9d8e83a307a5d71951a69f | |
parent | c8b248039ec1f75a7c5733bbe76d7fa416ce097a (diff) | |
download | nasm-f564874f49556d930882645a348fcd6ddc6847b0.tar.gz |
Don't opt out of sanitizers in third_party/nasm
This causes build problems with MSan because the opt-out does not quite work.
Start with the simple solution and see if just building it normally works. (If
NASM has bugs, may as well get them fixed.) If this causes issues, we can apply
a more targetted workaround.
Bug: 928357
Change-Id: I5260d16d3bcd42117eb4053b6916d29798494514
-rw-r--r-- | BUILD.gn | 8 |
1 files changed, 1 insertions, 7 deletions
@@ -5,13 +5,7 @@ import("//build/config/compiler/compiler.gni") import("nasm_sources.gni") -configs_to_delete = [ - # Don't enable sanitizers for build tools. They slow down the overall build. - "//build/config/sanitizers:default_sanitizer_flags", - - "//build/config/compiler:chromium_code", -] - +configs_to_delete = [ "//build/config/compiler:chromium_code" ] configs_to_add = [ "//build/config/compiler:no_chromium_code" ] if (is_debug) { configs_to_delete += [ |