Introduce an MSan blacklist and use it to ignore V8.

BUG=330709,178409
TBR=glider@chromium.org,eugenis@chromium.org

Review URL: https://codereview.chromium.org/141943002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245597 0039d316-1c4b-4281-b951-d872f2087c98

build/common.gypi

@@ -371,6 +371,7 @@
       # MemorySanitizer only works with clang, but msan=1 implies clang=1
       # See http://clang.llvm.org/docs/MemorySanitizer.html
       'msan%': 0,
+      'msan_blacklist%': '<(PRODUCT_DIR)/../../tools/msan/blacklist.txt',
 
       # Use the dynamic libraries instrumented by one of the sanitizers
       # instead of the standard system libraries.
@@ -934,6 +935,7 @@
     'asan_coverage%': '<(asan_coverage)',
     'lsan%': '<(lsan)',
     'msan%': '<(msan)',
+    'msan_blacklist%': '<(msan_blacklist)',
     'tsan%': '<(tsan)',
     'tsan_blacklist%': '<(tsan_blacklist)',
     'use_instrumented_libraries%': '<(use_instrumented_libraries)',
@@ -3512,6 +3514,7 @@
                   '-fsanitize=memory',
                   '-fsanitize-memory-track-origins',
                   '-fPIC',
+                  '-fsanitize-blacklist=<(msan_blacklist)',
                 ],
                 'ldflags': [
                   '-fsanitize=memory',

tools/msan/blacklist.txt

+# The rules in this file are only applied at compile time.
+# Because the Chrome buildsystem does not automatically touch the files
+# mentioned here, changing this file requires clobbering all MSan bots.
+#
+# Please think twice before you add or remove these rules.
+
+# V8 is blacklisted until it can properly support MSan. http://crbug.com/330709
+src:*/v8/src/*