One of the automated build tests on an Intel HD4600 GPU on Windows fails due to OpenCL compilation failures. The test and results are e.g. here:
http://ci.arrayfire.org:8010/#/builders/16/builds/5
All tests failing use the GEMM kernel, so that seems to be the issue.
34 - clblast_test_xgemm (Failed)
35 - clblast_test_xsymm (Failed)
41 - clblast_test_xtrmm (Failed)
42 - clblast_test_xtrsm (Failed)
47 - clblast_test_xgemmbatched (Failed)
48 - clblast_test_xgemmstridedbatched (Failed)
49 - clblast_test_override_parameters (Failed)
51 - clblast_test_preprocessor (Failed)
There are some regular incorrectness errors as well, but also some compilation related things. Examples of outputs for ./clblast_test_xgemm include a regular -11 compilation error, but als output like:
fcl build 1 succeeded.
fcl build 2 succeeded.
Error: parse error.
Not sure how to debug this. Is the latest driver installed, do other OpenCL programs work well? Perhaps more info would be found when running a non-test program (since errors are caught), e.g. ./clblast_client_xgemm?
Or, perhaps the device needs to be tuned for specifically, although I'm not sure since some cases do seem to pass...?
Perhaps @umar456 can help out a bit as well?
One of the automated build tests on an Intel HD4600 GPU on Windows fails due to OpenCL compilation failures. The test and results are e.g. here:
http://ci.arrayfire.org:8010/#/builders/16/builds/5
All tests failing use the GEMM kernel, so that seems to be the issue.
There are some regular incorrectness errors as well, but also some compilation related things. Examples of outputs for
./clblast_test_xgemminclude a regular -11 compilation error, but als output like:Not sure how to debug this. Is the latest driver installed, do other OpenCL programs work well? Perhaps more info would be found when running a non-test program (since errors are caught), e.g.
./clblast_client_xgemm?Or, perhaps the device needs to be tuned for specifically, although I'm not sure since some cases do seem to pass...?
Perhaps @umar456 can help out a bit as well?