[$] Concurrency bugs should fear the big bad data-race detector (part 1)

The first installment of the"big bad" series described how a compiler can optimize your concurrentprogram into oblivion, while the second installment introduceda tool to analyze small litmus tests for such problems. Those twoarticles can be especially helpful for training, designdiscussions, and checking small samples of code. Although suchautomated training and design tools are welcome, automated codeinspection that could locate even one class of concurrency bugs would beeven better. In this two-part article, we look at a tool to do that kindof analysis.