The Unexplored Terrain of Compiler Warnings

TL;DR

This paper discusses the importance and underutilization of compiler warnings in industry, highlighting their potential for early bug detection and the need for more focused research to evaluate their true cost-benefit balance.

Contribution

It identifies the gap between the perceived value of compiler warnings and the industry's inconsistent practices, emphasizing the need for systematic research.

Findings

Addressing compiler warnings early is beneficial.

Industry practices vary from silencing warnings to zero-tolerance.

More focused research is needed to assess cost-benefit.

Abstract

The authors' industry experiences suggest that compiler warnings, a lightweight version of program analysis, are valuable early bug detection tools. Significant costs are associated with patches and security bulletins for issues that could have been avoided if compiler warnings were addressed. Yet, the industry's attitude towards compiler warnings is mixed. Practices range from silencing all compiler warnings to having a zero-tolerance policy as to any warnings. Current published data indicates that addressing compiler warnings early is beneficial. However, support for this value theory stems from grey literature or is anecdotal. Additional focused research is needed to truly assess the cost-benefit of addressing warnings.