Hey,
Yes, we could do that. The drawback is longer compilation when only vectors
are needed. For example, I can resolve my circular dependency problem by
adding #include "viennacl/matrix.hpp" above #include "viennacl/vector.hpp"
in "tests/vector_float_double.cpp" Including "matrix.hpp" in the gene
Hey,
> Yes, I feel like we would to do this whenever the vector and matrix
> kernels are handled by the same backend ( generator, blas linker, or
> whatever). Indeed, there are some operators in matrix_base so it will be
> complicated to split things up. The core circular dependency seems to be
>
Hi,
Yes, I feel like we would to do this whenever the vector and matrix kernels
are handled by the same backend ( generator, blas linker, or whatever).
Indeed, there are some operators in matrix_base so it will be complicated
to split things up. The core circular dependency seems to be in the
sche
Hi,
> This has been a nightmare to make the opencl kernels device-specific.
> I'm facing a dependency problem which traits cannot solve. The reason is
> the following:
>
> -> The kernel generator requires some traits (row_major(), size(),
> internal_size2(), etc.)
> -> The generator is now includ
Hi!
This has been a nightmare to make the opencl kernels device-specific. I'm
facing a dependency problem which traits cannot solve. The reason is the
following:
-> The kernel generator requires some traits (row_major(), size(),
internal_size2(), etc.)
-> The generator is now included in linalg/o
