On 8/17/2009 16:30, Ozkan Sezer wrote: > On Mon, Aug 17, 2009 at 10:49 AM, JonY<10wa...@gmail.com> wrote: >> Hi, >> >> This patch will add warning flags. >> >> There are currently 5 warning levels, which defaults to level 3. It gets >> noisier for higher levels. Level 0 is equivalent to no additional flags. Use >> "--with-warnings[=n]" to set the levels. >> >> I really wanted -Werror by default, so you can stop to see *all* the >> warnings, but its too strict for buildbot. >> >> The warning levels can still be fine tuned. If needed, there can also be >> more warning levels. >> >> Comments? > > This is a good one. I'd also suggest that you remove the > default -Wno-strict-aliasing flag from Makefile.am. And also > yocan increase the -Wstrict-aliasing level with increased > level of warning to -Wstrict-aliasing=2, say at level four? >
Hi, yeah, I was about to remove the -Wno-strict-aliasing but forgot. For the -Wstrict-aliasing level, <http://gcc.gnu.org/onlinedocs/gcc-4.4.1/gcc/Warning-Options.html> says 3 is the default, with 2 being less accurate but faster and 1 being prone to false positives. Level 4 already uses -Wstrict-aliasing=2. There is also a C++ specific warning flag, though I haven't come across any important warnings. I added it for completeness. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
