Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[olemars]

Does Windows automatically link to dlls hidden somewhere in your system files? I ran the program as-is, unzipped into a folder, which worked for me.
I think I have the SDK installed, but that's it. The SDK for AMD, and AMD's catalyst driver.

DLL's are searched for and loaded according to the environment path variable, but it always checks the current directory first (where the executed program is), so if you ship a dll with your application it will always choose that dll.

With linking I meant what libraries you link with when you build the program (linker->input in visual studio project properties). You link with .lib files which have a matching .dll. If you accidentally shpi the program with a dll of another version than the .lib you linked with there will be issues.

In this case the problem is actually with the GPU platform. I have an NVIDIA card that only supports OpenCL 1.0. You'll have to check at startup that the computer/GPU the application is running on supports the OpenCL level you need (there are specific functions for doing that).

Edit: Also, you shouldn't include OpenCL.dll with the program. If the installed driver supports any form of OpenCL it will have its own dll available. When you include it yourself you override the one shipped with the driver, which will cause additional problems (including issues between OS versions).

[Nadaka]

Does Windows automatically link to dlls hidden somewhere in your system files? I ran the program as-is, unzipped into a folder, which worked for me.
I think I have the SDK installed, but that's it. The SDK for AMD, and AMD's catalyst driver.

http://msdn.microsoft.com/en-us/library/7d83bc18%28v=vs.80%29.aspx

[Skyrunner]

I don't see how checking for the openCL version can help o_O It's not like I can have another version of the code ready to go. And it's linked at startup, so the version checking provided with OpenCL doesn't work..

[olemars]

I don't see how checking for the openCL version can help o_O It's not like I can have another version of the code ready to go. And it's linked at startup, so the version checking provided with OpenCL doesn't work..

Checking for version lets you at least quit gracefully with a meaningful message on unsupported hardware. If you use device subdivision you probably require at least OpenCL 1.1, possibly 1.2.  In many cases it's actually possible to have several code paths available for different hardware, it's quite common to have a number of fallbacks depending on i.e. shader capabilities or specific OpenGL extensions.

The version checking should work as long as you don't distribute your own OpenCL.dll along with your executable (since that'll report the OpenCL on your build machine, not the one you're trying to run it on).

[Skyrunner]

Don't plan on using device subdivision, so that should go fine.



Wait, did it work without the OpenCL dll I included? Right now, all the program has is a bunch of clGetDeviceInfo calls.

[olemars]

I got the same crash with your dll and the one I have from NVidia. According to Depends you call the following functions from the dll:

Code: [Select]

clRetainDevice
clReleaseDevice
clGetDeviceInfo
clGetDeviceIDs
clGetPlatformIDs
It's the first two that are causing problems.

[Skyrunner]

Weird. I don't even call those. :S Maybe it's part of the C++ binding I'm using...?
The ones I explicitly call are the latter three.

[olemars]

http://www.khronos.org/registry/cl/api/1.2/cl.hpp

Yep, that seems to be it. The reference helpers are different depending on these defines in cl.h

Code: [Select]

/* OpenCL Version */
#define CL_VERSION_1_0                              1
#define CL_VERSION_1_1                              1
#define CL_VERSION_1_2                              1
Unfortunately that means it's locked to 1.2 at compile time. You'll have to set CL_VERSION_1_2 and possibly CL_VERSION_1_1 to 0 in cl.h and rebuild, depending on what hardware you need to run on.
The hardware conformancy list is available here: http://www.khronos.org/conformance/adopters/conformant-products/

I also just realized I need a new computer My GT240 only supports 1.0 while most anything else seems to at least support 1.1 by now.

[Skyrunner]

Yeah, my own Radeon HD Series 6000 supports up to 1.1. Can you see if this works on your PC?

With macro. Might work?

[olemars]

Same crash. Where did you put the macro?

[Skyrunner]

At the very top of the cl.hpp, after #ifndef CL_HPP_ part. I don't think CL_VERSION_1_0 is defined anywhere else...

[olemars]

It'll have to be after #include <CL/opencl.h>
Set these two to 0

Code: [Select]

#define CL_VERSION_1_1    0
#define CL_VERSION_1_2    0
edit:
Actually you should probably #undef them instead.

[Skyrunner]

Okay, here it is again. Link

Sorry for cluttering up the thread with this problem, other denizens of self.isCoder() D:

[olemars]

They'll cope :p

See last edit. Either comment out those two from cl.h or #undef them right after opencl.h is included.

The C++ binding uses

Code: [Select]

#if defined(CL_VERSION_1_2)
instead of just

Code: [Select]

#if CL_VERSION_1_2
And I'm really inclined to consider that a bug in OpenCL.

[Skyrunner]

Am I doing this right?

http://pastebin.com/87ZUe64p

I'm not sure why defined next to #if is blue, but defined next to #define isn't... @_@