------- Comment #16 from manu at gcc dot gnu dot org 2008-07-30 09:26 ------- I think -Wundefined should warn for any potential undefined and unspecified behaviour. I know they are not the same according to the standard but for a practical point of view they both result in a behaviour that is not properly defined and may change without notice. Most users do not know the difference and I would argue that most of them don't even care. Having to distinct flags would be cumbersome.
There are a few warnings already in GCC that would fall under this definition and most of them are enabled by default and unconditionally. Therefore, this warning should probably also be enabled by default as -Woverflow is. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30334
