On Mon, Mar 04, 2013 at 10:51:53AM +0100, Nils Philippsen wrote: > > Yes, either downgrading "-O3" to "-O2", or getting rid of > "-ffast-math" (or more specifically, one of "-fno-math-errno > -funsafe-math-optimizations -ffinite-math-only" which are switched on > with -ffast-math) makes the binary work for me again with gcc 4.7.2.
-ffast-math: "This option is not turned on by any -O option besides -Ofast, since it can result in incorrect output for programs that depend on an exact implementation of IEEE or ISO rules/specifications for math functions. It may, however, yield faster code for programs that do not require the guarantees of these specifications." Or more succintly from an older version of that documentation: "Might allow some programs designed to not be too dependent on IEEE behavior for floating-point to run faster, or die trying." Since neither UFRaw nor Lensfun are deliberately designed this way (and doing so would require also tracking GCC changes to see what else might break with each new compiler version), I think it's reasonable to say it's not a bug for UFRaw to fail when compiled with that option. -O3 should always be fine though. Martin ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ ufraw-devel mailing list ufraw-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ufraw-devel
