Hi Karl,
sounds great!
No reason to hurry :-)
Best regards
Andreas
Hi Andreas,
- good news:
I made good progress on introducing a generic context. For code lines
such as
viennacl::vectorT x = y + z;
the vector x is created in the correct context (i.e. deduced from y, z).
This
Hi Phil,
Thanks Karl !
This will allow serve us when we deal with multiple GPU ;)
I'm pretty happy with the model now, basically extending the concept of
a 'context' in OpenCL beyond OpenCL boundaries: Create vectors as follows:
viennacl::vectorT x(42); //vector in default context
Hi again !
The generator code is pushed on the master branch.
2013/7/28 Karl Rupp r...@iue.tuwien.ac.at
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
Hi guys,
as I was recently discussing asynchronous transfer and execution with
Evan in an MPI context, this is now addressed with
viennacl::async_copy()
Typical use case:
std::vectordouble std_x(SIZE);
viennacl::vectordouble vcl_x(SIZE);
viennacl::async_copy(std_x, vcl_x); // same
