Hi Oswin, >> FYI: ViennaCL 2.x will provide all functionality via a shared C >> library in order to make cases such as the one you describe much >> easier. This means that there will be stable function names for all >> operations. An optional C++ layer will sit on top, rather than the >> other way round as it is the case now... > > Oh this sounds great! I am in no hurry, I can wait for this. Is there > some way I can help to make this happen? I am not good in OpenCL/CUDA > but I am pretty decent when it comes to C++, so if I can help speed up > the process...
thanks for the offer. C++-wise things are pretty much settled, most of the work to come is actually in low-level optimizations in each of the three backends. Still, any kind of feedback (improvements to API, performance regressions, bugreports, etc.) is highly appreciated and equally important. Most of the updates to ViennaCL in the near future relate to better performance (ViennaCL 1.7.x) and extending some functionality only available in the OpenCL-backend to the other backends (1.8.x). I think this will take until about the end of the year. 2.0.0 will be quite a leap, so it may take until around April 2016 to have it released. There will be a separate development branch for early feedback, though. :-) Best regards, Karli ------------------------------------------------------------------------------ _______________________________________________ ViennaCL-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/viennacl-devel
