From: Patrik J. <co...@fa...> - 2010-02-24 19:02:39
|
I suspect this has to do with aggressive optimization and comparing floating-point results. Could you try printing out the lhs and rhs and manually assess what the discrepancy is? just add "cout << array_1(sin(a)(1,Range::all()) << array_1(array_2(sin(a))(1,Range::all()))". I worried about comparing the results by equality for exactly this reason, but since there is no blitz reduction "nearenough", it's more painful. cheers, /Patrik On Tue, Feb 23, 2010 at 7:22 AM, hughgs <hu...@du...> wrote: > > With optimization turned on, I'm getting a couple of failures in make > testsuite while running expression-slicing.exe. I've isolated the > first failure to this line: > > test_expr(sin(a)(1,Range::all()), array_2(sin(a))(1,Range::all())); > > If I compile, in the testsuite directory, with the optimization flags on, > expression-slicing.exe fails at the above line. > > $ g++ -DHAVE_CONFIG_H -I. -I.. -I.. -g -DBZ_DEBUG -O3 -funroll-loops -fstrict-aliasing -fomit-frame-pointer -ffast-math -o expression-slicing.exe expression-slicing.cpp -L../lib/.libs -lblitz > $ ./expression-slicing.exe > Test failed: expression-slicing.cpp line 35 > > Interestinly, I can get past that line if I don't compile with O3 > optimization: > > $ g++ -DHAVE_CONFIG_H -I. -I.. -I.. -g -DBZ_DEBUG -O0 -funroll-loops -fstrict-aliasing -fomit-frame-pointer -ffast-math -o expression-slicing.exe expression-slicing.cpp -L../lib/.libs -lblitz > $ ./expression-slicing.exe > $ > > > The second error has the exact same symptons except it's related to this > line: > > test_expr(Laplacian2D(sin(a))(1,Range::all()), > array_2(Laplacian2D(sin(a)))(Range(1,1),Range::all())); > > > One other thing I tried was to substitute cos() and exp() functions but > the failure still occurs when compiling with the -O3 flag. I'm compiling > with gcc 4.3.4 under Cygwin for Windows. Any ideas. Thanks. > > > George S. Hugh > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Blitz-support mailing list > Bli...@li... > https://lists.sourceforge.net/lists/listinfo/blitz-support > |