Posted by Michael Bien on Aug 09, 2011; 11:34pm
URL: https://forum.jogamp.org/some-stuff-doesn-t-work-AMD-Windows-7x64-tp3237922p3240777.html

  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/