search for: dfp_abstolerance

...f > -O0 -ffp-contract=on > > They are not passing at: > -Ofast -ffp-contract=on > -Ofast -ffp-contract=off Let's separate completely FP-contract and fast-math. They're different things and need different solutions. > if(TEST_SUITE_USES_FAST_MATH) > add_definitions(-DFP_ABSTOLERANCE=1e0) > else() > add_definitions(-DFP_ABSTOLERANCE=1e-5) > endif() This doesn't make sense. If my program decreased precision by 5 orders of magnitude with -ffast-math, I'd be *very* worried. I hope that fast-math in Clang isn't that broken, so that's probably to do with...

On Wed, Oct 12, 2016 at 10:53 AM, Hal Finkel <hfinkel at anl.gov> wrote: > I don't think that Clang/LLVM uses it by default on x86_64. If you're using -Ofast, however, that would explain it. I recommend looking at -O3 vs -O0 and make sure those are the same. -Ofast enables -ffast-math, which can legitimately cause differences. > The following tests pass at "-O3" and

...p-contract=on >> > -Ofast -ffp-contract=off >> >> Let's separate completely FP-contract and fast-math. They're >> different >> things and need different solutions. >> >> >> > if(TEST_SUITE_USES_FAST_MATH) >> > add_definitions(-DFP_ABSTOLERANCE=1e0) >> > else() >> > add_definitions(-DFP_ABSTOLERANCE=1e-5) >> > endif() >> >> This doesn't make sense. If my program decreased precision by 5 >> orders >> of magnitude with -ffast-math, I'd be *very* worried. > > Is this an absol...

Hey folks, Some progress has been made since the first thread: http://lists.llvm.org/pipermail/llvm-dev/2017-March/111129.html And also I think the consensus is to enable "-ffp-contract=on" by default (instead of "fast"), which seems to be working on some preliminary tests I made. I just ran the test-suite on x86_64 and AArch64. The former is ok, the latter still has some