Displaying 4 results from an estimated 4 matches for "fitsinlegalinteger".
2012 Jan 24
0
[LLVMdev] load widening conflicts with AddressSanitizer
...ed by load widening]
Once the Attribute::AddressSafety is set by clang (a separate patch),
fixing this bug may look as simple as this:
--- lib/Analysis/MemoryDependenceAnalysis.cpp (revision 148708)
+++ lib/Analysis/MemoryDependenceAnalysis.cpp (working copy)
@@ -323,6 +323,14 @@
!TD.fitsInLegalInteger(NewLoadByteSize*8))
return 0;
+ if (LI->getParent()->getParent()->hasFnAttr(Attribute::AddressSafety)
&&
+ LIOffs+NewLoadByteSize > MemLocEnd) {
+ // We will be reading past the location accessed by the original
program.
+ // While this is safe in a r...
2015 Jul 01
2
[LLVMdev] Deriving undefined behavior from nsw/inbounds/poison for scalar evolution
----- Original Message -----
> From: "Bjarke Roune" <broune at google.com>
> To: "Hal Finkel" <hfinkel at anl.gov>
> Cc: llvmdev at cs.uiuc.edu, "Jingyue Wu" <jingyue at google.com>
> Sent: Wednesday, July 1, 2015 2:27:59 PM
> Subject: Re: [LLVMdev] Deriving undefined behavior from nsw/inbounds/poison for scalar evolution
>
>
2011 Dec 28
2
[LLVMdev] load widening conflicts with AddressSanitizer
________________________________
From: Kostya Serebryany [kcc at google.com]
Sent: Wednesday, December 28, 2011 2:46 PM
To: Criswell, John T
Cc: llvmdev at cs.uiuc.edu
Subject: Re: [LLVMdev] load widening conflicts with AddressSanitizer
On Wed, Dec 28, 2011 at 12:40 PM, Criswell, John T <criswell at illinois.edu<mailto:criswell at illinois.edu>> wrote:
Dear All,
I think adding
2012 Jan 24
4
[LLVMdev] load widening conflicts with AddressSanitizer
...ay of just hiding the real
problem, which seems to be that address sanitizer is overly strict.
Ciao, Duncan.
>
> --- lib/Analysis/MemoryDependenceAnalysis.cpp (revision 148708)
> +++ lib/Analysis/MemoryDependenceAnalysis.cpp (working copy)
> @@ -323,6 +323,14 @@
> !TD.fitsInLegalInteger(NewLoadByteSize*8))
> return 0;
> + if (LI->getParent()->getParent()->hasFnAttr(Attribute::AddressSafety) &&
> + LIOffs+NewLoadByteSize > MemLocEnd) {
> + // We will be reading past the location accessed by the original program.
> + //...