On Jan 14, 2010, at 1:17 AM, Krzysztof Kosiński wrote:
put in some extra code in configure.ac to turn off strict aliasing warnings when boost::optional emits a lot of them. It tries to compile a short snippet using boost::optional with -Werror=strict-aliasing, and if it fails, it adds -Wno-strict-aliasing to CXXFLAGS. It might be a bit unsafe
Also... can you pinpoint exactly what situation causes the warnings you mentioned?
I've not noticed any showing up.
So if you have hidden a class of warnings, we probably need to make sure it is only hidden for those combinations where the spurious warnings actually show up. For all other combinations we *really* want to leave them enabled. Instead of turning off warnings, we want to turn more on.
For example, when I turned on warnings for unused parameters, I literally hit one out of a hundred that was not benign. *However*, those ones ended up being significant, and being able to see them allowed us to correct some long standing but subtle bugs.