Martin Dybdal:
> On 20 February 2012 16:39, Paul Sujkov wrote:
>> Ah, it seems that I see now what's going wrong way. I'm not using the 'run'
>> function from the CUDA backend, and so by default I guess the code is
>> interpreted (the test backend used for semantics check). However, it's not
>> pe
On 20 February 2012 16:39, Paul Sujkov wrote:
> Ah, it seems that I see now what's going wrong way. I'm not using the 'run'
> function from the CUDA backend, and so by default I guess the code is
> interpreted (the test backend used for semantics check). However, it's not
> perfectly clear how to
Ah, it seems that I see now what's going wrong way. I'm not using the 'run'
function from the CUDA backend, and so by default I guess the code is
interpreted (the test backend used for semantics check). However, it's not
perfectly clear how to use CUDA backend explicitly.
If you have any suggestio
Yep. It doesn't help:
generateArray1 n = Acc.use $ Acc.fromList (Acc.Z Acc.:. n*n*n) [0..n*n*n]
still takes the same amount of time. I guess something's wrong elsewhere.
On 20 February 2012 16:06, Alex Gremm wrote:
> Hi Paul,
>
> even though I just started reading about Accelerate, it seems to
Hi Alex,
I've seen that method, but I don't see how can I use it for initialization
purposes. It creates Acc (Array e i) from Array e i, but what should I do
while I don't have Array yet? And when Array is already initialized, 'use'
will transfer it to GPU memory which will add some extra timings,
Hi everyone,
since accelerate mail list seems to be defunct, I'm trying to ask specific
questions here. The problem is: array initialization in
Data.Array.Accelerate takes a 10x amount of time in contrast to both
Data.Array and bare C++ CUDA array initialization. This can be due to
Data.Array.Acce
