https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30334
Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msebor at gcc dot gnu.org --- Comment #17 from Martin Sebor <msebor at gcc dot gnu.org> --- I agree with the goal of detecting undefined behavior but I don't think a catchall warning option like -Wundefined would be very helpful. Not all kinds of undefined behavior are of the same severity so providing a single option for all of it would make it hard to clean up code with more than just a handful of instances of it. Especially for late warnings that are susceptible to false positives, being able to control them in a targeted way is important. The trend over the last years has been toward providing granular warning options to control the detection of specific/related kinds of problems, like -Warray-bounds, or -Wuninitialized.