gmp and its friends mpfr and mpc are used for all
numerical calculations. You could perhaps set
bignum-precision to 64 to mimic C doubles, and
get faster float calculations.
___
Cmdist mailing list
Cmdist@ccrma.stanford.edu
https://cm-mail.stanford.edu
Hmm, looking a bit at the code now, and most likely, the
scheme math operations in Radium probably takes
significantly less time than other things. Math
speed probably doesn't matter, so I'm going
to try to enable gmp for a while.
On Fri, Apr 14, 2017 at 1:54 PM, Kjetil Matheussen wrote:
> Tha
Thank you. How about float vs. integer? Is gmp
used only for integers, or is it used for floats as well?
In Radium, I think only calculations with floating
points are important to be fast. And only
integer calculations needs to be accurate. Big-number
accuracy for floating points are probably not
In the gmp version, it's probably safest to assume
everything is going through gmp. In cases where the
optimizer can ascertain ranges, s7 will use
faster code, but I just tore out half the optimizer,
and am rebuilding it. So I don't know how the
in-between stuff interacts with gmp -- give me a
mo
On Thu, Apr 13, 2017 at 9:05 PM, wrote:
> Let me
> know if the gc protection functions are too slow --
> internally in s7, I sometimes use the scheme stack
> for quick GC protection, especially when I can't
> guarantee I'll reach the unprotect code -- that
> process could be exported.
When using
