Matt Borland
Matt Borland
@NAThompson A section to use as many threads as processors available has been added. With the range of benchmark maxed out at 2^30 it bench marks at 6.86 N/0.69N
I added an additional unit test for the multi-threading section and added this set of tests to the Jamfile. Are the 2 thread tests ok to send to CI or...
@NAThompson I can't personally tell you a use case for `prime_range`, but the functionality is available in other libraries like [sympy](https://docs.sympy.org/latest/modules/ntheory.html#sympy.ntheory.generate.primerange). Locally `-fsanitize=thread` and `fsanitize=address` are both clean.
Superseded by #370
Superseded by #370
You are correct that we should be checking for `nullptr` dereference to avoid UB. I'll take a look at your implementation and adjust accordingly.
@NAThompson Since you got this to work previously for 128 bit float do you see anything obvious I am missing? Error for incomplete type [here](https://github.com/boostorg/math/runs/7708438647?check_suite_focus=true#step:13:7155).
@NAThompson This is good for review. I pulled 128 bit support into it's own header otherwise you would have to link quadmath anytime you used `next.hpp`.
Here are the before and after benchmarks @NAThompson : ``` Original performance (Boost 1.80.0): Unable to determine clock rate from sysctl: hw.cpufrequency: No such file or directory This does not...
> @mborland : Does it need a `fast_float_distance` header? Could we not just improve the performance of the current implementation? The float and double cases improve upon the current implementation....