Forum > GPU crunching

Latest drivers (NVidia and ATI)

<< < (39/167) > >>

Jason G:
Hi Mark,
   Short answer: No.

Long answer:
   Cuda SDKs & Libraries from 3.0 onwards are 'strongly versioned'.  That means apps built with a certain SDK are meant to be used with certain DLLs.  The New SDK with New DLLs will require a new App.
I would not advise playing swippy swappy with DLLs, as was possible in the past.  You could get lucky and it works, but if you break it you own both parts  ;)  Also, the 3.2 SDK is so far accessible to registered developers only, and is under NDA, so no-one will be posting Cuda 3.2 DLLs around here while I'm on watch  ;D

msattler:

--- Quote from: Jason G on 16 Sep 2010, 06:07:21 pm ---Hi Mark,
   Short answer: No.

Long answer:
   Cuda SDKs & Libraries from 3.0 onwards are 'strongly versioned'.  That means apps built with a certain SDK are meant to be used with certain DLLs.  The New SDK with New DLLs will require a new App.
I would not advise playing swippy swappy with DLLs, as was possible in the past.  You could get lucky and it works, but if you break it you own both parts  ;)  Also, the 3.2 SDK is so far accessible to registered developers only, and is under NDA, so no-one will be posting Cuda 3.2 DLLs around here while I'm on watch  ;D



--- End quote ---
Short response: OK, mate.

Long response:  Understood......I did not realize that NDA applied, I would not ask anybody to break that here.
I will hold my kibble until you guys play with it a bit and nvidia makes it freely available.
I was going offa the last experience we had when a simple dll upgrade made lots more crunching.

Jason G:
LoL,
   Yeah I strongly suspect. it's that DLL swippy-swappying going on all over the place that prompted nVidia to make the changes. I can imagine all the nVidia call-centre help desk people being fooded with 'My Cuda broke' calls because 2.2 & 2.3 weren't 100% functionally identical, but worked for most purposes with 2.3 DLLs under 2.2 or earlier builds with increased performance.

It's pretty hard to diagnose what the problem is if something crashes, when the app was built with some Cuda version, but the libraries are goodness knows what version.

A quick rebuild on the weekend should indicate if something should be put through express testing ready fior 3.2 release.  I'm guessing at this point it might be able to wait until a bit more streamlining & fine tuning is done, as I'm not expecting a huge difference,, but never know, I've been surprised before.

msattler:
Best of luck with it......
You can PM me if you want me to give it a go.

Meow meow.

perryjay:
Yeah, what Mark said!  You know me, always running around here in a state of mass confusion but willing to try!   ;D

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version