On 5 April 2012 11:16, Arnaud Charlet wrote: > > OK, the above list looks reasonable to me at least as a starting point > that could be a bit refined (not sure -Wstrict-aliasing is so useful by > default for instance for legacy code),
-Wstrict-aliasing is only active when -fstrict-aliasing is on, and if that's on the warning definitely should be, since it indicates code that may well misbehave, "legacy" or not.
