[L2Ork-dev] A plea for full double precision support out of the box in Purr data
Yoann Le BORGNE
yoann.le.borgne at free.fr
Sun Aug 20 19:25:42 UTC 2017
> Are you using katja's Pd double repo?
>
> If you're just changing the value of t_float, then there are a number
> of objects (like [osc~]) which are not computing
> the correct output.
I'm compiling Pd 0.48 with a dedicated flag. While browsing
makefile.gnu, I saw
# You can add compiler flags using CODECFLAGS, MORECFLAGS and/or
MORELDFLAGS.
# For example, you can turn off optimizing and enable debugging:
CODECFLAGS=-g
# or *compile with native double precision: MORECFLAGS=-DPD_FLOATSIZE=64*
This flag enables double precision as discussed here and when asked
about in Pd's mailing list, IOhannes M Zmölnig said it was
"experimental". Indeed some objects are not computing the correct output
but /some are/ and the fact that there is now a compiler flag for this
is a good thing as it means that it is still a work in progress.
I don't know for how long it has been there though, as I've been
compiling Pd only a few times, following the readme and there seems to
be no reference of this in Pd's release notes history.
Yoann
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxaudio.org/pipermail/l2ork-dev/attachments/20170820/d3e77644/attachment.html>
More information about the L2Ork-dev
mailing list