Now that we are testing things, the GPU stuff has to actually work instead of
just being a facade for funding agencies that think GPUs are worth spending
money on ;-)
> On Feb 2, 2018, at 11:32 PM, Smith, Barry F. wrote:
>
>
> Thanks. I'll try to be patient.
>
>
>> On Feb 2, 2018, at 1
Thanks. I'll try to be patient.
> On Feb 2, 2018, at 11:28 PM, Karl Rupp wrote:
>
>
Why can't the VECCUDA type coexist with the VECCUSP or VECVIENNACL types?
If it can't coexist, can the code be reworked to allow it to coexist?
>>>
>>> Currently it can't coexist because some var
Why can't the VECCUDA type coexist with the VECCUSP or VECVIENNACL types? If it
can't coexist, can the code be reworked to allow it to coexist?
Currently it can't coexist because some variables are conditionally compiled
and may be multiply defined (e.g. spptr).
Hmm, I don't think so. T
> On Feb 2, 2018, at 11:10 PM, Karl Rupp wrote:
>
> Hey,
>
>>I'm am totally confused by
>> 1) the existence of veccuda.py
>
> if I remember correctly, its purpose is to make sure that one of the GPU
> backends is enabled if a user configures --with-cuda.
>
>
>> 2) the fact that veccuda
Hey,
I'm am totally confused by
1) the existence of veccuda.py
if I remember correctly, its purpose is to make sure that one of the GPU
backends is enabled if a user configures --with-cuda.
2) the fact that veccuda.py depends on some packages but is not a package and
is not in packa
I'm am totally confused by
1) the existence of veccuda.py
2) the fact that veccuda.py depends on some packages but is not a package and
is not in packages/
Why can't the VECCUDA type coexist with the VECCUSP or VECVIENNACL types? If it
can't coexist, can the code be reworked to allow it t
