Hi Philippe, > I'm slowly getting back to ViennaCL. > I have added one bullet point to the roadmap: > * Full integration of the micro-scheduler and the generator
Yep, definitely. See issue #8, it's already on the TODO-list for the 1.5.x branch. The nice thing is that this is completely internal work, so we can switch over without doing anything harmful to the public API. > I will be working on cleaning GEMM (i.e. better integration of the > multiple BLAS backends, and harmonize the kernels using the > column&trans<->row¬rans identity.) until I go back to France, in 1 > week. I'll comment on this on the other thread you started. > I have also noticed that the size checking could be moved upwards > in the dispatching mechanism, for now, they are duplicated between > opencl/cuda/openmp . My initial intention was to check the sizes only in the common layer, but I failed to apply this consistently and hence used double checking at some point. Feel free to move this to the generic dispatcher routines. > Once this is done, I will probably work towards the > full integration of the micro-scheduler. Can we get rid of op_executor<>? As soon as the micro-scheduler is working, op_executor is obsolete. I think we will need to have both around for a very short time-frame to do all the testing and verifications. Best regards, Karli ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ ViennaCL-devel mailing list ViennaCL-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viennacl-devel
