Closed GoogleCodeExporter closed 8 years ago
Looking at test_radixsort.cpp in cudpp_testrig, I note that we test with many
non-multiple-of-16 sizes:
size_t test[] = {39, 128, 256, 512, 513, 1000, 1024, 1025, 32768,
45537, 65536, 131072, 262144, 500001, 524288,
1048577, 1048576, 1048581, 2097152, 4194304,
8388608};
Can you first run the testrig and see if it works properly for you, and then
replace one of the test[] items with 3991 and see if it works too? That would
help to isolate the problem.
Original comment by jow...@gmail.com
on 16 Dec 2010 at 5:13
Hi
I ran test rig and also changed one of the values to arbit values as my
simulation throws onto the CUDPP library (3991, 3642 etc.). That didn't create
any problems in the testrig (All tests passed).
However now i also see that this error pops up but i also see in the error log
that stores the result of cudaGetErrorString (cudaGetLastError()) that the
mersenne twister random number generator also flags an unknown error.
But after a couple of kernels flag this error and this kernel in the log showed
"no error" this error of radix sort pops up.
Which makes me think the error is somewhere else and the asynchronous nature of
error reporting is probably confusing me?
Do you think so too? Thanks for your prompt reply and help.
rohit
Original comment by itabhiya...@gmail.com
on 17 Dec 2010 at 9:37
Hi
I tried commenting each function one by one and only time when i don't get
errors is when i comment ONLY the declaration(and destroy) of Cudppplan for
sort and calling cudppsort.
This only happens when i pass values of n other than 4096 (my starting value,
after that the number of elements to sort decreases by 17 every time i declare
a new plan in every new iteration)
SO n keeps changing. all other kernels uncommented and cudpp calls commmented
makes my code run.
and the error is the same as i have written before.
thanks
Original comment by itabhiya...@gmail.com
on 17 Dec 2010 at 2:35
Hi Rohit,
Can you please send me your complete code sample implementing cudpp. I will try
and reproduce the issue.
Thanks,
Ritesh
Original comment by rites...@gmail.com
on 31 Jan 2011 at 6:40
No response and insufficient info. Closing.
Original comment by harr...@gmail.com
on 6 Jul 2011 at 2:16
Original issue reported on code.google.com by
itabhiya...@gmail.com
on 16 Dec 2010 at 4:05