[ViennaCL-devel] Kernel Generator wrap-up

Hello everybody, I'm proud to announce that after about 3weeks, I've recoded from scratch the OpenCL code generator to integrate it fully with viennacl::scheduler::statement. That being said, I'm entering the point where I need to inquire your opinion for (many) further design choices. Sorted by

Re: [ViennaCL-devel] Kernel Generator wrap-up

Hey, I'm proud to announce that after about 3weeks, I've recoded from scratch the OpenCL code generator to integrate it fully with viennacl::scheduler::statement. hurray :-) With the changes to the generator I pushed yesterday there is now a clear spot on where to hand the expression over to

Re: [ViennaCL-devel] Kernel Generator wrap-up

Hey, My preferred option is to pad by default and either to make the padding a multiple of four or sixteen. However, we need to maintain a full set of unpadded operations, because user-provided buffers need not be padded (and a subsequent padding may be too expensive) I

[ViennaCL-devel] Scheduler datastructure changes

Hey, see commit message here: https://github.com/viennacl/viennacl-dev/commit/1a214259f577acd1b329197285e26cf2cd774e34 Best regards, Karli -- See everything from the browser to the database with AppDynamics Get