Bug #2933
closedcompiler warning gags need better granularity
100%
Description
At present, for several reasons, we have gagged some high-value (and some low-value) compiler warnings globally. This really sucks, many of these warnings are just in general good things to have, others are things that people would like to more usefully opt-in to (it is likely opt-in works now, via explicitly re-stating -Wfoo, but nobody does this).
We should gag warnings down at the level that the gag is necessary to maintain a clean build, and allow people to work on removing the high-value gags.
Certain warnings still require a global gag, at least:
Wno-unknown-pragms -our code is littered with Studio-specific pragmasWno-array-bounds -This is based on an optimization pass which, should it misfire, will false-positive this warning in ways that can be sadly impossible to fix.
It is possible that -Wno-array-bounds, all the same, should be pushed down and just people made generally aware that it may not actually be possible to fix their code.
This is a massive, massive, massive amount of tedious work, unfortunately.
Updated by Rich Lowe over 10 years ago
- % Done changed from 70 to 100
- Status changed from In Progress to Resolved
Resolved in r13834 commit:58bc6f85b799