You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, the new algos are in develop and the original algos are less-commonly available, but are still present in the get_specfun_running_in_ci branch.
Based on the detailed discussion in #135, the following test case (shown below) leads to partly unusual behavior for the
sin()
function.The bahaviors are:
cpp_double_fp< 8-byte-double >
. OK.cpp_double_fp< 4-byte-float >
.eval_sin()
for new (Briggs/Shoup-style) algorithms (add/sub/mul/div) forcpp_double_fp< 4-byte-float >
.Getting the wrong answer in 2 does not really bother me due to the low precision of the composite type.
But crashing in 3 or seg-faulting, etc. does bother me. It would be nice if possible to see what's going on there.
Cc: @sinandredemption and @cosurgi
The text was updated successfully, but these errors were encountered: