search for: addresssanitizeralgorithm

...sists of a LLVM compiler plugin which performs simple code instrumentation and a malloc replacement library. The main advantage of the new tool is high speed: the slowdown is usually within 2x-2.5x. Detailed description of the algorithm is found here: http://code.google.com/p/address-sanitizer/wiki/AddressSanitizerAlgorithm The tool is young, but it already can run the Chromium browser (interactively!) and find bugs in it. Would the LLVM community be interested in adopting this code into the LLVM trunk? The instrumentation pass is ~350 LOC ( http://code.google.com/p/address-sanitizer/source/browse/trunk/llvm/AddressS...

...plugin which performs simple code > instrumentation and a malloc replacement library. > The main advantage of the new tool is high speed: the slowdown is usually > within 2x-2.5x. > Detailed description of the algorithm is found here: > http://code.google.com/p/address-sanitizer/wiki/AddressSanitizerAlgorithm > The tool is young, but it already can run the Chromium browser > (interactively!) and find bugs in it. > > Would the LLVM community be interested in adopting this code into the LLVM > trunk? > The instrumentation pass is ~350 LOC ( > http://code.google.com/p/address-sanitizer...

...LVM compiler plugin which performs simple code instrumentation and a malloc replacement library. > The main advantage of the new tool is high speed: the slowdown is usually within 2x-2.5x. > Detailed description of the algorithm is found here: http://code.google.com/p/address-sanitizer/wiki/AddressSanitizerAlgorithm > The tool is young, but it already can run the Chromium browser (interactively!) and find bugs in it. > > Would the LLVM community be interested in adopting this code into the LLVM trunk? > The instrumentation pass is ~350 LOC (http://code.google.com/p/address-sanitizer/source/brows...

...that checks for llvm coding style (similar to cpplint <http://google-styleguide.googlecode.com/svn/trunk/cpplint/>)? Documentation: everything is in the wiki. The main pages are: http://code.google.com/p/address-sanitizer/wiki/AddressSanitizer http://code.google.com/p/address-sanitizer/wiki/AddressSanitizerAlgorithm "who is going to maintain": my team at Google (in particular, myself and Alexander, in CC) are highly motivated to keep this working. "Do you have particular clients": the Chromium project is a very active<http://blog.chromium.org/2011/06/testing-chromium-addresssanitizer-fa...

On Jun 21, 2011, at 8:05 AM, Kostya Serebryany wrote: > Hi, > What would be our next steps in getting ASan into the LLVM trunk? > I'd like to do it in two steps, first for the LLVM part with minimal tests and then for the run-time library and all tests. > The current ASan's source repository will probably stay the primary home for the run-time library and tests as we plan

...s simple code >> instrumentation and a malloc replacement library. >> The main advantage of the new tool is high speed: the slowdown is usually >> within 2x-2.5x. >> Detailed description of the algorithm is found here: >> http://code.google.com/p/address-sanitizer/wiki/AddressSanitizerAlgorithm >> The tool is young, but it already can run the Chromium browser >> (interactively!) and find bugs in it. >> >> Would the LLVM community be interested in adopting this code into the LLVM >> trunk? >> The instrumentation pass is ~350 LOC ( >> http://code.g...

...fective ones. Kostya, maybe you can send the code by myself and/or Nick to help walk through it for style issues? Documentation: everything is in the wiki. The main pages are: > http://code.google.com/p/address-sanitizer/wiki/AddressSanitizer > http://code.google.com/p/address-sanitizer/wiki/AddressSanitizerAlgorithm > It would be good to have these written up in HTML for easy inclusion in the existing LLVM documentation tree. This tree is checked in along side the code itself. However, contributing snapshots of the documentation from the wiki page could likely occur in follow-up patches. Alternatively, may...

On 16 June 2011 09:27, Kostya Serebryany <kcc at google.com> wrote: > Question to the LLVM developers: would you consider adding > the AddressSanitizer code to the LLVM trunk? Do you have an idea how hard would it be to port to non-x86 platforms? I saw some Intel ASM in the C++ file... The run-time library being 1.5k loc is not encouraging, but it didn't look particularly

...At some point the file had no asm at all, but using the custom asm allows to make the generated code more compact. Now, the code that actually reports the error is 5-6 bytes, we could decrease it to 1 byte (at least on x86/x86_64) with some more work. http://code.google.com/p/address-sanitizer/wiki/AddressSanitizerAlgorithm#Report_Error My first attempt that used no asm required ~15 bytes of code. Note, this code is executed only once, so it affects the performance very slightly (through icache size). > > The run-time library being 1.5k loc is not encouraging, but it didn't > look particularly platform...

...aybe you can send the code by > myself and/or Nick to help walk through it for style issues? > > Documentation: everything is in the wiki. The main pages are: >> http://code.google.com/p/address-sanitizer/wiki/AddressSanitizer >> http://code.google.com/p/address-sanitizer/wiki/AddressSanitizerAlgorithm >> > > It would be good to have these written up in HTML for easy inclusion in the > existing LLVM documentation tree. This tree is checked in along side the > code itself. However, contributing snapshots of the documentation from the > wiki page could likely occur in follow-up...