diff options
| author | Alexey Samsonov <vonosmas@gmail.com> | 2014-05-29 01:44:13 +0000 |
|---|---|---|
| committer | Alexey Samsonov <vonosmas@gmail.com> | 2014-05-29 01:44:13 +0000 |
| commit | dea76ee889248deb7b0754d4ac3b9e6575e00b6c (patch) | |
| tree | 75429614877398b1a01218412b70542620b06f53 | |
| parent | c054d9813c9c7f8f2c95d78bc171bf761d2e73fc (diff) | |
| download | bcm5719-llvm-dea76ee889248deb7b0754d4ac3b9e6575e00b6c.tar.gz bcm5719-llvm-dea76ee889248deb7b0754d4ac3b9e6575e00b6c.zip | |
[ASan] Hoist blacklisting globals from init-order checking to Clang.
Clang knows about the sanitizer blacklist and it makes no sense to
add global to the list of llvm.asan.dynamically_initialized_globals if it
will be blacklisted in the instrumentation pass anyway. Instead, we should
do as much blacklisting as possible (if not all) in the frontend.
llvm-svn: 209790
| -rw-r--r-- | llvm/lib/Transforms/Instrumentation/AddressSanitizer.cpp | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/llvm/lib/Transforms/Instrumentation/AddressSanitizer.cpp b/llvm/lib/Transforms/Instrumentation/AddressSanitizer.cpp index ae51179a300..1730cff325a 100644 --- a/llvm/lib/Transforms/Instrumentation/AddressSanitizer.cpp +++ b/llvm/lib/Transforms/Instrumentation/AddressSanitizer.cpp @@ -1069,8 +1069,6 @@ bool AddressSanitizerModule::runOnModule(Module &M) { // Determine whether this global should be poisoned in initialization. bool GlobalHasDynamicInitializer = DynamicallyInitializedGlobals.Contains(G); - // Don't check initialization order if this global is blacklisted. - GlobalHasDynamicInitializer &= !BL->isIn(*G, "init"); StructType *NewTy = StructType::get(Ty, RightRedZoneTy, NULL); Constant *NewInitializer = ConstantStruct::get( |
