[PD-dev] double precision Pd: .patch files, tests and benchmarks

[Hans-Christoph Steiner]

Sounds great.  I'm happy to help setup a git repo if you want me too.   
github and gitorious are pretty straightforward to get the initial  
repo, then it would be a matter of pushing the pure-data.git to that  
repo, and starting work from there.  I think it makes sense to work  
off of pure-data.git rather than pd-extended.git since this is a patch  
targetted at getting into Miller's repo.

As for arch issues, I think Intel and ARM are the big ones to test  
these days.  But PPC is fine too.

.hc

On Oct 2, 2011, at 5:24 PM, katja wrote:

> Hi Hans,
>
> Thanks for your detailed comments. I will go through the code once
> again, you're right it's not as clean as could be.
>
> Regarding your suggestion to set up a repo, it seems to be the most
> logical thing to do. This could be considered a temporary branch for
> the double precision thing, to be discontinued once all the code works
> fine for single and double precision alike and merged into Pd. I'll
> start that up one of these days (my first repo ever, hope to get it
> done...).
>
> A few words on the scope of tests done so far. Rewritten code was
> developed and tested on Intel core CPU's, where it seems to work
> smooth, both with SSE and FPU instructions. Regarding functionality
> and robustness, I have good confidence that it will work anywhere, as
> it's simple and depends only on standard libs. But considering
> performance, more checking is needed. The rewritten phase-wrapping
> classes have branches in the perform-loops. These are only executed in
> rare cases, therefore branch prediction mechanisms can do their good
> work. But on older architectures branching may be more expensive. That
> was also the reason for Miller's branchless design of these classes,
> of course. PPC in particular should be considered, as there are still
> quite a few users. Maybe the code needs some finetuning to PPC. Only
> after settling this aspect, I would consider submitting the
> double-precision-ready .patch file for Pd's core code. Otherwise I'd
> risk an endless series of amendements on a submitted patch. In the
> meantime, double precision ready code would be available from this git
> repo we're planning.
>
> Katja
>
> _______________________________________________
> Pd-dev mailing list
> Pd-dev at iem.at
> http://lists.puredata.info/listinfo/pd-dev



----------------------------------------------------------------------------

"Making boring techno music is really easy with modern tools, but with  
live coding, boring techno is much harder." - Chris McCormick