[petsc-dev] Not possible to do a VecPlaceArray for veccusp

[Karl Rupp]

Hi Jose and Alejandro,

how's your current progress/status? It looks like I'm able to spend some 
time on this and can get this done by early next week. On the other 
hand, if you've finished all the relevant parts you required, I will 
refrain on duplicating the work.

Best regards,
Karli



On 02/28/2016 05:54 PM, Jose E. Roman wrote:
>
>> El 28 feb 2016, a las 10:45, Karl Rupp <rupp at iue.tuwien.ac.at> escribió:
>>
>> Hi,
>>
>>> I like the idea of having separate VECCUDA and VECVIENNACL, because it is possible to implement VECCUDA without dependence on a C++ compiler (only the CUDA compiler).
>>
>> I don't understand this part. NVCC also requires a C++ host compiler and is fairly picky about the supported compilers.
>
> You are right. I was thinking of the case when one has a pure C code and wants to use a --with-language=C PETSc configuration.
>
>>
>>
>>> If you want, we can prepare a rough initial implementation of VECCUDA in the next days, and we can later discuss what to keep/discard.
>>
>> Any contributions are welcome :-)
>>
>>
>>> Karl: regarding the time constraints, our idea is to present something at a conference this summer, and deadlines are approaching.
>>
>> Ok, this is on fairly short notice considering the changes required. I recommend to start with copying the CUSP sources and migrate it over to VECCUDA by replacing any use of cusp::array1d to a raw CUDA handle. Operations from CUSP should be replaced by CUBLAS calls.
>
> Ok. Will start work on this.
>
> Jose
>
>>
>> Best regards,
>> Karli
>>
>