search for: sanitizethread

...rtain passes)? >>> >> >> Yes. AddressSanitizer and ThreadSanitizer disable load widening that >> would create a partially out-of-bounds or a racy access. >> See lib/Analysis/MemoryDependenceAnalysis.cpp (search for >> Attribute::SanitizeAddress and Attribute::SanitizeThread). >> This case with MemorySanitizer is slightly different because we are not >> fighting a false positive, but rather a debug-info-damaging optimization. >> >> --kcc >> >> >>> If not, does this need some deeper discussion about alternatives (is it >&...

...gt;> >>> >>> Yes. AddressSanitizer and ThreadSanitizer disable load widening that >>> would create a partially out-of-bounds or a racy access. >>> See lib/Analysis/MemoryDependenceAnalysis.cpp (search for >>> Attribute::SanitizeAddress and Attribute::SanitizeThread). >>> This case with MemorySanitizer is slightly different because we are not >>> fighting a false positive, but rather a debug-info-damaging optimization. >>> >>> --kcc >>> >>> >>>> If not, does this need some deeper discussion abo...

...;> >>>> Yes. AddressSanitizer and ThreadSanitizer disable load widening that >>>> would create a partially out-of-bounds or a racy access. >>>> See lib/Analysis/MemoryDependenceAnalysis.cpp (search for >>>> Attribute::SanitizeAddress and Attribute::SanitizeThread). >>>> This case with MemorySanitizer is slightly different because we are not >>>> fighting a false positive, but rather a debug-info-damaging optimization. >>>> >>>> --kcc >>>> >>>>> >>>>> If not, does this...

...> >>>> Yes. AddressSanitizer and ThreadSanitizer disable load widening that >>>> would create a partially out-of-bounds or a racy access. >>>> See lib/Analysis/MemoryDependenceAnalysis.cpp (search for >>>> Attribute::SanitizeAddress and Attribute::SanitizeThread). >>>> This case with MemorySanitizer is slightly different because we are not >>>> fighting a false positive, but rather a debug-info-damaging optimization. >>>> >>>> --kcc >>>> >>>> >>>>> If not, does this nee...

...gt;> Yes. AddressSanitizer and ThreadSanitizer disable load widening > >>>> that would create a partially out-of-bounds or a racy access. > >>>> See lib/Analysis/MemoryDependenceAnalysis.cpp (search for > >>>> Attribute::SanitizeAddress and Attribute::SanitizeThread). > >>>> This case with MemorySanitizer is slightly different because we are > >>>> not fighting a false positive, but rather a debug-info-damaging > optimization. > >>>> > >>>> --kcc > >>>> > >>>>> >...

...gt; >>>> Yes. AddressSanitizer and ThreadSanitizer disable load widening >>>> that would create a partially out-of-bounds or a racy access. >>>> See lib/Analysis/MemoryDependenceAnalysis.cpp (search for >>>> Attribute::SanitizeAddress and Attribute::SanitizeThread). >>>> This case with MemorySanitizer is slightly different because we are >>>> not fighting a false positive, but rather a debug-info-damaging optimization. >>>> >>>> --kcc >>>> >>>>> >>>>> If not, does this...

...;> >>>> Yes. AddressSanitizer and ThreadSanitizer disable load widening >>>> that would create a partially out-of-bounds or a racy access. >>>> See lib/Analysis/MemoryDependenceAnalysis.cpp (search for >>>> Attribute::SanitizeAddress and Attribute::SanitizeThread). >>>> This case with MemorySanitizer is slightly different because we are >>>> not fighting a false positive, but rather a debug-info-damaging optimization. >>>> >>>> --kcc >>>> >>>>> >>>>> If not, does this...

...dressSanitizer and ThreadSanitizer disable load widening > > >>>> that would create a partially out-of-bounds or a racy access. > > >>>> See lib/Analysis/MemoryDependenceAnalysis.cpp (search for > > >>>> Attribute::SanitizeAddress and Attribute::SanitizeThread). > > >>>> This case with MemorySanitizer is slightly different because we > > >>>> are > > >>>> not fighting a false positive, but rather a debug-info-damaging > > >>>> optimization. > > >>>> > > >&g...

...gt;> Yes. AddressSanitizer and ThreadSanitizer disable load widening > >>>> that would create a partially out-of-bounds or a racy access. > >>>> See lib/Analysis/MemoryDependenceAnalysis.cpp (search for > >>>> Attribute::SanitizeAddress and Attribute::SanitizeThread). > >>>> This case with MemorySanitizer is slightly different because we > >>>> are > >>>> not fighting a false positive, but rather a debug-info-damaging > >>>> optimization. > >>>> > >>>> --kcc > >&gt...

...nitizer disable load > > >>>> widening > > >>>> that would create a partially out-of-bounds or a racy access. > > >>>> See lib/Analysis/MemoryDependenceAnalysis.cpp (search for > > >>>> Attribute::SanitizeAddress and Attribute::SanitizeThread). > > >>>> This case with MemorySanitizer is slightly different because > > >>>> we > > >>>> are > > >>>> not fighting a false positive, but rather a > > >>>> debug-info-damaging > > >>>> opt...

...gt;> Yes. AddressSanitizer and ThreadSanitizer disable load widening > >>>> that would create a partially out-of-bounds or a racy access. > >>>> See lib/Analysis/MemoryDependenceAnalysis.cpp (search for > >>>> Attribute::SanitizeAddress and Attribute::SanitizeThread). > >>>> This case with MemorySanitizer is slightly different because we are > >>>> not fighting a false positive, but rather a debug-info-damaging > optimization. > >>>> > >>>> --kcc > >>>> > >>>>> >...

...///< Stack protection required. StackProtectStrong, ///< Strong Stack protection. + SafeStack, ///< Safe Stack protection. StructRet, ///< Hidden pointer to structure to return SanitizeAddress, ///< AddressSanitizer is on. SanitizeThread, ///< ThreadSanitizer is on. diff --git a/include/llvm/InitializePasses.h b/include/llvm/InitializePasses.h index 2964798..76e44f4 100644 --- a/include/llvm/InitializePasses.h +++ b/include/llvm/InitializePasses.h @@ -235,6 +235,7 @@ void initializeRegionOnlyPrinterPass(PassRegistry&)...