You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I have trouble running kernels which are using the OpenCL 2.0 feature enqueue_kernel. The offline compilation runs without errors, but dispatching raises a runtime exception: kfd kfd: Invalid PPR device 0:1.0 pasid 1 address 0x0 flags 0x124
Device-enqueue requires OpenCL runtime which is not available with the CLOC flow. Recall you are compiling CL code to HSAIL, and then runnign that on HSA runtime. Practically this means that most OpenCL language features are available (ie local memory, atomics, instructions) but features that require an OpenCL runtime are not (two examples are device enqueue and printf).
Hi,
HSAIL provides instructions to work with user-mode-queues, such as addqueuewriteindex, casqueuewriteindex etc. Is there a reason for CLOC not to use these instructions? Semantics should be the same for HSAIL and OCL (at least for CLK_ENQUEUE_FLAGS_NO_WAIT).
On the other hand, CLOC does not produce any warning message. Instead, it produces a lot of HSAIL (which I haven't reverse-engineered yet).
Look at the cloc readme to see how to use the snack.sh command to generate the hsa API code to launch a kernel compiled by cloc. As Ben said earlier, we don't have the host side opencl API for HSA or ROCM machines.
Hi,
I have trouble running kernels which are using the OpenCL 2.0 feature
enqueue_kernel
. The offline compilation runs without errors, but dispatching raises a runtime exception:kfd kfd: Invalid PPR device 0:1.0 pasid 1 address 0x0 flags 0x124
Sourcecode:
System setup:
The text was updated successfully, but these errors were encountered: