[cfe-dev] OpenCL C
renato.golin at linaro.org
Tue Dec 17 08:11:21 PST 2013
On 17 December 2013 14:09, Nagy-Egri Máté Ferenc <nagymatef at freemail.hu>wrote:
> I would disagree on the “OpenCL users have mixed feelings” part, infact
> it’s just the contrary. One of the biggest flaws of SPIR is that there is
> no standard way of generating it from OpenCL C. Each vendor will have their
> own generator that will most likely be tuned for their own compilers. This
> might not be deliberate, but will happen, as the same people will be
> writing the C and the SPIR compilers. Having an unbiased SPIR generator is
> definately beneficial.
While most sensible people would agree with you, there are lawyers
(chuckle) and they make technical decisions. There are many people that
*know* how sensible this is, but still advocate the opposite because
they're told so. Once software patents, copyright, and all that jazz gets
fixed, we'll be able to go back to being sensible. But I digress...
As to going further, generating binary (or platform dependant intermediate)
> from OpenCL C should be left to the end-user, but that IMHO should not
> affect OpenCL C being declared as a supported language.
Absolutely! But someone has to own it, and most interested parties won't,
because they have their own front- and back-ends. Sigh...
At least we know of a few folks that are interested (you, Pekka, Clover
guys), so I think it's up to you guys to make that evolve into a fully
Note that the "support" part is complicated. "Patches welcome" is not
really acceptable when you claim compatibility, you have to fix some of the
mess yourself, because the user will report and won't be able to fix it
(sometimes, you won't even want his patch!).
Having a code owner is paramount to that, as Pekka said. But there is
something even more important: continuous integration. You must have a
reference platform, a good battery of tests, running continuously on every
commit (ish) to make sure no one breaks anything, etc. Buildbots,
test-suites, benchmarks. You need open source libraries, so that all that
can happen upstream, and you need interested people fixing bugs, adding
I haven't seen this much from the OpenCL folks, and "requesting" it to be
listed as "supported" is not enough. Where there's a will, there's a way...
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cfe-dev