> From: gcc-ow...@gcc.gnu.org [mailto:gcc-ow...@gcc.gnu.org] On Behalf Of > Andrew Haley > > Assigning a negative literal to an unsigned variable is well-defined > standard C. Is it really appropriate to warn for correct code?
There is lots of cases where gcc warn construct in correct code. Think for instance at unused variables. I think this is the same kind of situation here: the construct is valid but for many (or at least some) users it's not something they are likely to use and might indicate an error. I think the rationale provided by Daniel is sound. Thomas Preud'homme