Search:

Type: Posts; User: Scali

Search: Search took 0.00 seconds.

  1. Re: Using AMD SDK with Nvidia driver and Nvidia samples with AMD

    Okay, so it seems the new 195 beta drivers fix the problem that nVidia had, with their OpenCL library using cdecl rather than stdcall.
    Very good.
  2. Re: Who will write the platform -> driver interface specs ?

    Ah yes, I hadn't checked their beta4 release yet. Just installed it, and indeed, they have clean names now.
    So I guess it's now up to nVidia, their next release needs to have stdcall AND undecorated...
  3. Re: Who will write the platform -> driver interface specs ?

    No, he said they would use the same calling convention.
    That still doesn't mean they'll use the same naming convention aswell.
    That's why I think a standardized .def file is very important. That...
  4. Re: Who will write the platform -> driver interface specs ?

    Sadly, even importing by name won't work, as nVidia and AMD use neither the same naming nor the same calling convention on Windows currently.
    See also this topic:
    viewtopic.php?f=28&t=2114
  5. Replies
    3
    Views
    2,708

    Re: How to report NVidia OpenCL driver problems?

    You could report it on nVidia's own forum:
    http://forums.nvidia.com/index.php?showforum=134
  6. Re: Conflicting calling and naming conventions AMD/nVidia

    Thanks Simon.
    What about the exported symbol names (and possibly ordinals) though?
    I was thinking, if Khronos would standardize the name of the DLL now (is it going to be OpenCL.dll or...
  7. Conflicting calling and naming conventions AMD/nVidia

    I've come across a nasty binary incompatibility between AMD's and nVidia's OpenCL SDKs for Windows, even though they are both OpenCL 1.0-comformant.
    nVidia just used the cl_platform.h as-is, while...
Results 1 to 7 of 8