https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69295
--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> --- On big-endian ppc64 ext/special_functions/hyperg/check_value.cc these tests fail: data167, toler167 on line 11579 max_abs_frac = 4.82864e-13 data171, toler171 on line 11579 max_abs_frac = 5.15741e-12 data172, toler172 on line 11579 max_abs_frac = 3.10473e-11 data173, toler173 on line 11579 max_abs_frac = 1.09304e-12 data197, toler197 on line 11579 max_abs_frac = 4.82864e-13 data201, toler201 on line 11579 max_abs_frac = 1.86001e-12 data202, toler202 on line 11579 max_abs_frac = 3.21576e-12 data203, toler203 on line 11579 max_abs_frac = 2.58658e-12 data204, toler204 on line 11579 max_abs_frac = 6.15743e-13 data206, toler206 on line 11579 max_abs_frac = 1.87073e-10 data207, toler207 on line 11579 max_abs_frac = 7.72796e-10 data208, toler208 on line 11579 max_abs_frac = 5.19491e-09 data209, toler209 on line 11579 max_abs_frac = 2.15517e-10 data231, toler231 on line 11579 max_abs_frac = 5.15741e-12 data232, toler232 on line 11579 max_abs_frac = 3.10473e-11 data233, toler233 on line 11579 max_abs_frac = 1.09304e-12 data236, toler236 on line 11579 max_abs_frac = 1.87073e-10 data237, toler237 on line 11579 max_abs_frac = 7.72796e-10 data238, toler238 on line 11579 max_abs_frac = 5.19491e-09 data239, toler239 on line 11579 max_abs_frac = 2.15517e-10 data241, toler241 on line 11579 max_abs_frac = 1.68813e-09 data242, toler242 on line 11579 max_abs_frac = 2.64594e-08 data243, toler243 on line 11579 max_abs_frac = 3.02697e-07 data244, toler244 on line 11579 max_abs_frac = 4.34529e-07 data245, toler245 on line 11579 max_abs_frac = 2.36511e-07 for special_functions/02_assoc_legendre/check_value.cc only one fails: data033, toler033 on line 1901 max_abs_frac = 2.75283e-13 Ed, we need to do something about this. Jakub asked: > Increase tolerance on the problematic subtests, or only do that conditionally > on excess precision, or avoid testing altogether for excess precision, or > force flags like -ffloat-store to avoid excess precision? I'm leaning towards adding -ffloat-store so we don't use any excess precision (since that causes the results to match the values Ed generated using GSL, presumably on x86_64).
