Skip to content

Conversation

@dingfengshi
Copy link

In some cases (such as when there are a large number of points), executing convolution operations can result in illegal memory access errors. The reason is that the kernel responsible for computing the kmap has not completed execution before launching the next operation, leading to unpredictable memory access. To address this issue, an additional synchronization step is added to wait for the previous kernel to finish. This ensures that the next operation does not start until the preceding kernel has completed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant