Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

WebCLCommandQueue.enqueueNDRangeKernel does not accept globalWorkOffset = null #8

Open
Maratyszcza opened this issue Aug 8, 2014 · 0 comments
Open

WebCLCommandQueue.enqueueNDRangeKernel does not accept globalWorkOffset = null #8

Maratyszcza opened this issue Aug 8, 2014 · 0 comments

Comments

@Maratyszcza
Copy link

By standard, globalWorkOffset = null is a legitimate value (moreover, a default one). Chromium-WebCL complains about non-indexable value when enqueueNDRangeKernel is called with globalWorkOffset === null
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Maratyszcza