search for: heapoverflow

...://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html) > - It's helpful to compile with -O2, otherwise the pass will get confused > very quickly. The design of the analysis assumes at least a few > simplifications were done before. > OK, I just compiled it with -O2 and the heapoverflow protection have been triggered. Though, I don't know what is the simplification required for the pass to run correctly? > - Sometimes LLVM transforms loops into intrinsics, like memcpy or memset. > Right now these are not checked (but should, though) > - Guards are mostly not hoisted...

Hi Pierre, I'm the author of the BoundsChecking pass. It's true there's little documentation about it (only mentioned in: http://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html#availablle-checks). You can run it with 'clang -fsanitize=bounds' or 'opt -bounds-checking'. The BoundsChecking pass, AddressSanitizer and BaggyBoundsCheck are all different code bases,

Hi, I am a final year French student doing an internship at the University of Portsmouth. As I was taking hands on AddressSanitizer I took a look at BoundsChecking (both are in the lib/Transforms/Instrumentation folder). I found nothing on it except for the LLVM Documentation and references to BaggyBoundsCheck (which is not the same project. As far as I understood it is part of the SAFECode