Re: [ViennaCL-devel] Roadmap to 1.6 : Cleaning the code, refurbishing the test suite, the benchmark suite, etc...

2014-08-17 Thread Philippe Tillet
Hey, 2014-08-17 11:52 GMT+02:00 Karl Rupp r...@iue.tuwien.ac.at: Hi, So it seems like most of the features are ready for ViennaCL 1.6. My merge from a few days ago (finally) fully integrated the use of device-specific kernels for BLAS1, BLAS2, BLAS3. hurray! :-) The reduction API

Re: [ViennaCL-devel] Roadmap to 1.6 : Cleaning the code, refurbishing the test suite, the benchmark suite, etc...

2014-08-17 Thread Karl Rupp
Hi, * nmf only implements matrixT, but in principle matrix_baseT should work (since no custom kernel is called, I believe) NMF uses a custom kernel and thus only works with OpenCL. A generalization to matrix_base should be straight-forward, yes. I should be able to do

Re: [ViennaCL-devel] Roadmap to 1.6 : Cleaning the code, refurbishing the test suite, the benchmark suite, etc...

2014-08-17 Thread Philippe Tillet
Hey, The nasty bug on strided GEMV got solved. I'm available on wednesday for the code uniformization session. We should be on IRC at the same time, though, in case we face a situation we had not discussed. I have a couple of questions regarding a standardized way of naming the numeric type of a

[ViennaCL-devel] Roadmap to 1.6 : Cleaning the code, refurbishing the test suite, the benchmark suite, etc...

2014-08-16 Thread Philippe Tillet
Hey! So it seems like most of the features are ready for ViennaCL 1.6. My merge from a few days ago (finally) fully integrated the use of device-specific kernels for BLAS1, BLAS2, BLAS3. The reduction API is still missing, though, but I think that the priority should be to polish the code, and to