Tomi Aarnio

For prioritization, we should first tackle those items that have the most severe impact on application portability from one WebCL implementation to another. Currently, applications must have separate code paths...

Some of the listed items are now implemented, some others not needed anymore due to spec changes. The following deviations still remain: - WebCLCallback + its usage in build() and...

Here's an updated list of what's still missing (off the top of my head): - The new forms of createContext; - WebCLEvent.setCallback; - WebCLException, correct exception names; - WebCLImage.getInfo; -...

Current status of missing features: - WebCLEvent callbacks (other callbacks are OK); - enableExtension and getSupportedExtensions. Missing features that require integrating the validator: - WebCLKernelArgInfo; - Kernel argument type checking;...

Confirmed, the browser crashes when closing the tab (Windows/NVIDIA/Firefox 34).

`console.log` should be available for Workers since Firefox 29. DEBUG() still doesn't seem to be working, though, because nothing shows up in the console. Need to investigate.

What's the value returned by `device.getInfo(WebCL.DEVICE_MEM_BASE_ADDR_ALIGN)` on the device that you're using? The error message suggests that it's going to be 1024, which means that sub-buffers must be aligned to...

@wolfviking0 Have you been able to fix or work around this issue?

The `clWaitForEvents` error is because WebCL and OpenCL both require events in a wait list to belong to the same context, see www.khronos.org/registry/cl/sdk/1.1/docs/man/xhtml/clWaitForEvents.html. If you're not getting CL_INVALID_CONTEXT in the...

That's weird. Can you post a link to your app so that I can debug?