some stuff doesn't work (AMD, Windows 7x64)

I have here this system:

Windows 7x64
Athlon II x4
AMD Radeon 5830
Catalyst 11.7
APP SDK 2.5
using jocl-0.9-b377-20110728-windows-i586.7z binaries

Of the online demos, only the info and the opengl/cl interop demo works, the other ones seem to have a CL_BUILD_PROGRAM_FAILURE error.

On my own code, I also get the CL_BUILD_PROGRAM_FAILURE when I use the CPU device, so there's probably a relation. On some of my newer code, I get JVM stackoverflow crashes that I haven't yet been able to track down (probably related to sloppy coding).

I have switched a while ago from the same AMD cpu with an Nvidia Fermi GPU where everything worked fine with the same "new" code (both AMD CPU and NV GPU OpenCL devices) using an older version of the APP SDK.

  On 08/09/2011 07:42 AM, gwarf [via jogamp] wrote: jocl will post the build log if the compilation failed. Does it show
something?

>   On some of my newer code, I get JVM
> stackoverflow crashes that I haven't yet been able to track down (probably
> related to sloppy coding).
a stackoverflow shouldn't be JOCL's fault since it does not deal much
with recursion. If you think it is JOCL's fault, please post the stack
trace and provide a test reproducing the issue if possible.


> I have switched a while ago from the same AMD cpu with an Nvidia Fermi GPU
> where everything worked fine with the same "new" code (both AMD CPU and NV
> GPU OpenCL devices) using an older version of the APP SDK.
it is possible that a OpenCL program which works on driver A will fail
on driver B. So you will have to test on all drivers if you take it serious.


regards,
michael

--
http://michael-bien.com/

As far as the CPU driver problem goes, all it says is "Internal Error:  as failed [error: CL_BUILD_PROGRAM_FAILURE]"
I have the exact same error on the JavaCL demos too, when using the CPU device.

I'm not so sure how to get a stacktrace for JVM crashes, they happen instantly at startup. I will probably try porting my code to C later on, it's most likely not related to JOCL, however I thought I should just mention it anyway and see what you have to say about it.

  On 08/10/2011 12:51 AM, gwarf [via jogamp] wrote:
> As far as the CPU driver problem goes, all it says is "Internal Error:  as
> failed [error: CL_BUILD_PROGRAM_FAILURE]"
> I have the exact same error on the JavaCL demos too, when using the CPU
> device.
"Internal Error" is not part of any JOCL exception message. Are you
using the low level api?
again: this is not the build log, thats the error code. If building a
program with CLProgram.build() fails you would get the build log too.
Please post a test case since its hard for me to guess what is going on
here.

> I'm not so sure how to get a stacktrace for JVM crashes, they happen
> instantly at startup.
segfaults... ok I see. As you said stackoverflow i had java
stackoverflows in mind. (testcase please)

>   I will probably try porting my code to C later on,
> it's most likely not related to JOCL, however I thought I should just
> mention it anyway and see what you have to say about it.
well, i would need more information to help you here. All i can say is
that the AMD SDK was so far very reliable for me on recent CPU devices
(e.g i7). I haven't tested on a Athlon II yet however.


driver re-installation might help on windows. Do the native amd SDK
samples work for you?

-michael

--
http://michael-bien.com/

This is all I get from it: (I also get warnings if there are any)
com.jogamp.opencl.CLException$CLBuildProgramFailureException:
CLDevice [id: 130748104 name: AMD Athlon(tm) II X4 635 Processor type: CPU profile: FULL_PROFILE] build log:
Internal Error:  as failed [error: CL_BUILD_PROGRAM_FAILURE]

I have reinstalled the drivers and the APP SDK already. The SDK examples and other apps work fine.

  On 08/10/2011 03:36 AM, gwarf [via jogamp] wrote:
> This is all I get from it: (I also get warnings if there are any)
> com.jogamp.opencl.CLException$CLBuildProgramFailureException:
> CLDevice [id: 130748104 name: AMD Athlon(tm) II X4 635 Processor type: CPU
> profile: FULL_PROFILE] build log:
> Internal Error:  as failed [error: CL_BUILD_PROGRAM_FAILURE]
Ok this makes sense. The Internal Error is in the compiler log, so the
source is the driver. This really looks like a driver bug. You should
get the same output if you paste your kernel into the AMD kernel analyzer.

there is not much i could do in jocl fix this :)

regards,

-michael