1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking.org

AddressSanitizer Being Ported To GCC Trunk

Compiler

Published on 11 October 2012 08:47 AM EDT
Written by Michael Larabel in Compiler
2 Comments

GCC developers continue to work on bringing AddressSanitizer, which is part of the LLVM project, to their open-source compiler in hopes of better catching memory bugs and errors.

Google's Diego Novillo has shared that a new transitional branch has been made in the process of porting ASAN to trunk. "I have created a temporary branch to host the port of ASAN to trunk. Wei has done the initial port of the original code from Kostya. It compiles but we still do not have the runtimes (Wei is working on that)."

ASAN is the AddressSanitizer that serves as a memory error detector for C and C++ codes. AddressSanitizer is capable of detecting memory bugs such as use-after-free, heap buffer overflows, stack buffer overflows, global buffer overflows, and use-after-return. One of the benefits of AddressSanitizer over alternatives like Valgrind is that ASAN is designed to be very fast. AddressSanitizer within LLVM/Clang serves as a compiler instrumentation module in the form of an LLVM pass and then a run-time library that overrides the memory allocation functions.

Running AddressSanitizer binaries lead to a reported slowdown of about 2x, which is still faster than similar memory checking tools. GNU Compiler Collection developers have been interested in AddressSanitizer support and there's been some work previously while now it seems to finally be coming together with this transitional branch as the current code is made compatible with the latest GCC trunk, which is needed before it can be merged.

The GCC ASAN run-time also then needs to be written before it's actually useful, but Diego mentions that it should come soon.

More information on AddressSanitizer (ASAN) is available from its Google Code page.

About The Author
Michael Larabel is the principal author of Phoronix.com and founded the web-site in 2004 with a focus on enriching the Linux hardware experience and being the largest web-site devoted to Linux hardware reviews, particularly for products relevant to Linux gamers and enthusiasts but also commonly reviewing servers/workstations and embedded Linux devices. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics hardware drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated testing software. He can be followed via and or contacted via .
Latest Linux Hardware Reviews
  1. The Power Consumption & Efficiency Of Open-Source GPU Drivers
  2. AMD R600g/RadeonSI Performance On Linux 3.16 With Mesa 10.3-devel
  3. Intel Pentium G3258 On Linux
  4. SilverStone Precision PS10
Latest Linux Articles
  1. Nouveau vs. Radeon vs. Intel Tests On Linux 3.16, Mesa 10.3-devel
  2. KVM Benchmarks On Ubuntu 14.10
  3. X.Org Server 1.16 Officially Released With Terrific Features
  4. Ubuntu With Linux 3.16 Smashes OS X 10.9.4 On The MacBook Air
Latest Linux News
  1. Linus Torvalds On GCC 4.9: Pure & Utter Crap
  2. Cauldron 2014: GCC & LLVM Will Look To Collaborate More
  3. GCC Receives ACM Programming Languages Software Award
  4. KDE 4.14 Beta 3 Released
  5. A New Video Has Us Real Excited About The New UT For Linux
  6. CoreOS Experiences Its First Stable Release
  7. GNOME 3.13.4 Continues Working On Wayland & More
  8. Wine 1.7.23 Has Initial Support For 64-bit Android Builds
  9. FreeBSD Developing A New Automounter, Other Features
  10. Guix 0.7 Can Now Install The GNU Operating System
Latest Forum Discussions
  1. Updated and Optimized Ubuntu Free Graphics Drivers
  2. Debian + radeonsi
  3. How To Setup Radeon DPM On Ubuntu Linux
  4. Open-source drivers on ATI R7 260X
  5. New build, first Linux PC, what could go wrong? ;)
  6. AMD "Hawaii" Open-Source GPU Acceleration Still Not Working Right
  7. Radeon related kernel bug??
  8. how the US intellegentia operates: