On Tue, 9 May 2023 at 23:38, Joel Sherrill wrote: > We are currently using gcc 12 and specifying C11. To experiment with > these stricter warnings and slowly address them, would we need to build > with a newer C version?
No, the proposed changes are to give errors (instead of warnings) for rules introduced in C99. GCC is just two decades late in enforcing the C99 rules properly! > What practices might the GCC community recommend to a project > wanting to discover the issues uncovered and slowly address them? I -Werror=implicit-int -Werror=implicit-function-declaration -Werror=int-conversion > i am a bit gun shy because I remember the move from GCC 3.3 to 3.4 > where the improved strict alias checking gave us a LOT of warnings to > deal with and it felt overwhelming. I don't want to do that again. > > But I believe in letting the compiler get stricter and find things. Defaulting > to stricter checking is a good thing. The checks are already done, they're just warnings by default, and so easily missed/ignored when compiling large code bases.
