PrivateMemorySpace array fields are being translated to Constant data arrays in OpenCL #11

Closed
opened 2022-09-05 16:07:52 +00:00 by CoreRasurae · 2 comments
CoreRasurae commented 2022-09-05 16:07:52 +00:00 (Migrated from git.qoto.org)

OpenCL private arrays are general purpose registers that are privately available for each thread in the compute unit, and as such those values can only be initialized from the kernel code itself, not the host, and they cannot be marked as belonging to the Constant memory space, which is simply wrong.
Currently Aparapi v3.0.0 tries to assign initialization values for them from the host and in the Constant memory space, which is completely wrong and can cause some kernels to fail during execution at host OpenCL driver. This needs to be fixed.

OpenCL private arrays are general purpose registers that are privately available for each thread in the compute unit, and as such those values can only be initialized from the kernel code itself, not the host, and they cannot be marked as belonging to the Constant memory space, which is simply wrong. Currently Aparapi v3.0.0 tries to assign initialization values for them from the host and in the Constant memory space, which is completely wrong and can cause some kernels to fail during execution at host OpenCL driver. This needs to be fixed.
CoreRasurae commented 2022-09-05 19:55:09 +00:00 (Migrated from git.qoto.org)

mentioned in merge request !26

mentioned in merge request !26
CoreRasurae commented 2023-10-24 18:04:44 +00:00 (Migrated from git.qoto.org)

mentioned in commit 9aff2e7408

mentioned in commit 9aff2e74085b9a0fe30f552fe82a37dde5e83832
CoreRasurae (Migrated from git.qoto.org) closed this issue 2023-10-24 18:04:44 +00:00
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
aparapi/aparapi#11
No description provided.