Google Parsing Of LLVM's Clang Compiler Errors
Written by Michael Larabel in Compiler on 21 November 2012 at 01:03 AM EST. Add A Comment
Another interesting session from this month's LLVM Developers' Meeting in San Jose was about how Google manages to collect and utilize Clang diagnostics internally for software they develop at the company.

Matt Beaumont-Gay of Google talked at the LLVM compiler conference about how they parse, store, and analyze the output of diagnostics (code warnings/errors) produced by LLVM. Google's in-house build system stores the output of all shared code-bases that occur. Matt ended up writing a MapReduce and using thje LLVM/Clang output as its input. "We now have a daily batch job that crunches through all of the compiler stderr from the last day, parses out detailed, structured information about the diagnostics that Clang produced, and writes the information into a database for later analysis."

For those interested, there are PDF slides on how Google leverages LLVM/Clang diagnostics and the most common compiler errors they hit with their internal code-bases.
About The Author
Author picture

Michael Larabel is the principal author of Phoronix.com and founded the site in 2004 with a focus on enriching the Linux hardware experience. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated benchmarking software. He can be followed via Twitter or contacted via MichaelLarabel.com.

Related Compiler News
Popular News
Trending Reviews & Featured Articles