[cfe-dev] OpenCL C
longguoping at gmail.com
Tue Dec 17 16:38:05 PST 2013
Nice work on pocl.
Just some personal thoughts.
From users perspective, what they need is OpenCL running on a vendor specific target device. The thing is, while the OpenCL standard is open, which means technically we could work out a production level frontend on top of Clang, the backend is usually vendor specific and proprietary. For the open source community developers, the limited accessibility to vendor specific target details makes it hard to produce a complete competitive solution for the end user. For device vendors, it's relatively easier to construct a OpenCL frontend with Clang.
This partially explains why there are so many alternative OpenCL solutions, yet there is still no competitive open source solution for the end user.
On Wednesday, December 18, 2013 at 6:37 AM, Pekka Jääskeläinen wrote:
> On 12/17/2013 07:12 PM, Renato Golin wrote:
> > Can we have that running as a buildbot?
> That would be great, but unfortunately it costs money to
> get the conformance suite and probably comes with NDAs.
> Perhaps it will be possible to get the suite by some
> means, and install a private buildbot for it at some point.
> For now I think a way to proceed would be to create a
> table like the mentioned http://clang.llvm.org/cxx_status.html
> for features described in the OpenCL 1.2 (and later 2.x)
> specs and start crossing out what is done. Perhaps
> refer to (sub)sections and even sentences in the
> specs that deal with the kernel language. I can
> start it when I get some time.
> About the vagueness of the specs. We can forward those
> issues to Khronos and hopefully they'll correct it
> in the future specs releases. Until that we just
> interpret the vague spots as we see fit?
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu (mailto:cfe-dev at cs.uiuc.edu)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cfe-dev