Hi Andreas,
> Have you reported this to Nvidia? (If not, you should.)
Well, as I mentioned, I did not manage to reproduce the bug in pure
Cuda, and reporting bug without the reproduction sequence is just rude
)
Anyway, this is no longer a blocker to me, since I have rewritten my
code (pycudafft,
On Dienstag 09 Februar 2010, Bogdan Opanchuk wrote:
> Hello,
>
> Yet another stupid question. Most probably, I missed something
> obvious, but anyway - can someone explain why I get some NaN's in
> output for the program (listed below)? Surprisingly, bug disappears if
> I send '1' instead of '-1'
Hello,
Yet another stupid question. Most probably, I missed something
obvious, but anyway - can someone explain why I get some NaN's in
output for the program (listed below)? Surprisingly, bug disappears if
I send '1' instead of '-1' as a third parameter to function (or remove
'int' parameters com