As far as I am concerned CUDA is total crap now.
My application uses the device driver api version of CUDA.
And the application/the cuda driver won’t even load the module.
It complains of some kind of floating point error.
I will upload the video so you can see the crap in action for yourself.
And I will make my app distributeable so you guys at nvidia can test and debug it for yourself.
Perhaps my processor is not supported any more by the device driver api… perhaps it’s using some new floating point operations inside intel processors.
And I will upload my app to my web folder in a moment… I’ll just change some folders and so forth.
This problem was also present in cuda 5.5.
Links will follow in a moment and then nvidia will look like shit… and so will I but I dont care about that last part. To bad that it came to this.
Video created. I am now looking into this problem further.
It seems the problem is in the just in time compiler inside the driver. My app uses the driver api which is ofcourse much better than runtime crap. Cause driver api allows multi threading and multi language.
I will now make one last video comparing cuda toolkit compiler versions.
To see if older does or does not work.
Ok I will spare you the secondary video. The 64 bit floating point version did work, but only with cuda toolkit 4.2 compiler and only for debug code, and even that run buggy… sometimes it wouldn’t ran at all which is new behaviour.
All other compiler versions and settings failed.
It’s completely obvious that cuda 5 and 6 has turned into MAJOR CRAP.
Get kernel ptx and source and app here to try for yourself:
Made this into a seperate topic…