Two questions: I've mostly been using -Wconversion privately to catch the occasional 32<->64 bit conversion bug... but I just graded the work of a student whose results got destroyed by an inadvertent implicit "double->int", and now I'm paranoid about my own codes. Would anyone mind me adding "-Wconversion" to the default libMesh warnings, even if we're not yet 100% clean in library code?
We don't currently add compiler warning flags to compilation in opt mode. Is there a reason why not? I'd have expected the extra compilation time spent generating warning flags to be dwarfed by the optimization work itself. --- Roy ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
