I just realized that we may depend on Khronos Vulkan and SPIR-V headers if we are going to implement some sort of fallback when OpenCL driver is not installed. The background is that OpenCL is not part of AOSP, but Google has confirmed that Vulkan will be available on Android in the future. In that case, we can compile OpenCL kernel to SPIR-V and pass it to Vulkan to achieve the fallback. Please take it into consideration that we will potentially host these headers as well.
BR Jiajie -----Original Message----- From: Crosswalk-dev [mailto:[email protected]] On Behalf Of Raphael Kubo da Costa Sent: Friday, August 28, 2015 9:27 PM To: [email protected] Subject: Re: [Crosswalk-dev] Intent to switch: using our own GitHub copy of the OpenCL headers "Hu, Jiajie" <[email protected]> writes: > OK.. I'm just expressing my own opinion, and I just want to keep > things consistent with WebGL / OpenGL. It's not quite a big issue for > me where the headers are hosted. Alright, in this case I'll move forward with hosting them in a separate repository. > You mentioned that you want to avoid adding new commits (especially > ones which have no chance of being upstreamed) to chromium-crosswalk, > this raises another concern for me. For historical reasons, by now > almost all WebCL code are located in src/WebKit/Source/modules/webcl, > and this minimizes the effort required during rebase. However, > strictly speaking this is not the right architecture because system > hardware is accessed within Blink. We are considering moving some code > from Blink to src/content and migrating to Chromium's multi-process > model gradually so that WebCL can be used on platforms other than > Android. This will apparently be a much more complex task than > committing the OpenCL headers (see how WebGL is implemented), so I'm > afraid that will be totally contrary to the philosophy of avoiding new > commits. Yeah, this is one big topic to discuss then. I don't have much to say at the moment; basically if we decide it's the way forward and it pays off there isn't a lot we can do other than try to minimise the changes we make to existing files (just like we do in Blink). _______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev _______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
