Displaying 4 results from an estimated 4 matches for "isinsanitizerblacklist".
2018 Feb 22
2
Memory sanitizer porting
...e source locations from being instrumented by the sanitizers.
Normally this works without issues, but I discovered that you cannot compile compiler-rt msan implementation with -fsanitize=memory even if the whole location is blacklisted (that much I can confirm from the invocations of CodeGenModule::isInSanitizerBlacklist function).
What happens is that for some reason memory sanitizer:
— still tries to partially instrument the blacklisted code;
— does not check whether its global memory storage variables are already defined.
The second issue, present in MemorySanitizer::initializeCallbacks, adds a second copy of st...
2018 Feb 22
0
Memory sanitizer porting
...eing instrumented by the
> sanitizers.
> Normally this works without issues, but I discovered that you cannot compile
> compiler-rt msan implementation with -fsanitize=memory even if the whole
> location is blacklisted (that much I can confirm from the invocations of
> CodeGenModule::isInSanitizerBlacklist function).
> What happens is that for some reason memory sanitizer:
> — still tries to partially instrument the blacklisted code;
> — does not check whether its global memory storage variables are already
> defined.
> The second issue, present in MemorySanitizer::initializeCallbacks,...
2018 Feb 25
1
Memory sanitizer porting
...the
>> sanitizers.
>> Normally this works without issues, but I discovered that you cannot compile
>> compiler-rt msan implementation with -fsanitize=memory even if the whole
>> location is blacklisted (that much I can confirm from the invocations of
>> CodeGenModule::isInSanitizerBlacklist function).
>> What happens is that for some reason memory sanitizer:
>> — still tries to partially instrument the blacklisted code;
>> — does not check whether its global memory storage variables are already
>> defined.
>> The second issue, present in MemorySanitizer::...
2014 Nov 03
8
[LLVMdev] [PATCH] Protection against stack-based memory corruption errors using SafeStack
...B.addAttribute(llvm::Attribute::StackProtectReq);
+ else if (LangOpts.getStackProtector() == LangOptions::SSPSafeStack)
+ if (!D->hasAttr<NoSafeStackAttr>())
+ B.addAttribute(llvm::Attribute::SafeStack);
// Add sanitizer attributes if function is not blacklisted.
if (!isInSanitizerBlacklist(F, D->getLocation())) {
diff --git a/lib/Driver/ToolChains.cpp b/lib/Driver/ToolChains.cpp
index 15e3ade..68528b7 100644
--- a/lib/Driver/ToolChains.cpp
+++ b/lib/Driver/ToolChains.cpp
@@ -10,6 +10,7 @@
#include "ToolChains.h"
#include "clang/Basic/ObjCRuntime.h"
#include...