<html>
<head>
<meta name="generator" content="Windows Mail 17.5.9600.20315">
<style data-externalstyle="true"><!--
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
}
p.MsoNormal, li.MsoNormal, div.MsoNormal {
margin:0in;
margin-bottom:.0001pt;
}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst,
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle,
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
line-height:115%;
}
--></style></head>
<body dir="ltr">
<div data-externalstyle="false" dir="ltr" style="font-family: 'Calibri', 'Segoe UI', 'Meiryo', 'Microsoft YaHei UI', 'Microsoft JhengHei UI', 'Malgun Gothic', 'sans-serif';font-size:12pt;"><div>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.</div><div><br></div><div>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.<br></div><div data-signatureblock="true"><br></div><div style="padding-top: 5px; border-top-color: rgb(229, 229, 229); border-top-width: 1px; border-top-style: solid;"><div><font face=" 'Calibri', 'Segoe UI', 'Meiryo', 'Microsoft YaHei UI', 'Microsoft JhengHei UI', 'Malgun Gothic', 'sans-serif'" style='line-height: 15pt; letter-spacing: 0.02em; font-family: "Calibri", "Segoe UI", "Meiryo", "Microsoft YaHei UI", "Microsoft JhengHei UI", "Malgun Gothic", "sans-serif"; font-size: 12pt;'><b>Feladó:</b> <a href="mailto:renato.golin@linaro.org" target="_parent">Renato Golin</a><br><b>Elküldve:</b> kedd, 2013. december 17. 14:34<br><b>Címzett:</b> <a href="mailto:pekka.jaaskelainen@tut.fi" target="_parent">Pekka Jääskeläinen</a><br><b>Másolat:</b> <a href="mailto:cfe-dev@cs.uiuc.edu" target="_parent">Clang Dev</a></font></div></div><div><br></div><div dir=""><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 17 December 2013 10:30, Pekka Jääskeläinen <span dir="ltr"><<a href="mailto:pekka.jaaskelainen@tut.fi" target="_parent">pekka.jaaskelainen@tut.fi</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px; border-left-style: solid;">I was wondering why OpenCL C is not listed in the Clang's<br>
supported languages in the front page? It's now quite well<br>
supported and is also a "C family language". Why it's not<br>
a "1st class language" in Clang/LLVM?<br></blockquote><div><br></div><div>Hi Pekka,</div><div><br></div><div>I may be completely wrong, but I think the OpenCL users have mixed feelings about a truly open source compiler. The lack of proper support in Clang (as you state), the existence of many other alternatives (like Clover and all proprietary ones) tells me that the support in Clang won't really fly unless someone cares enough about it.</div>
<div><br></div><div><br></div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px; border-left-style: solid;">Another thing is that I see no CODE_OWNERS.txt entry for<br>
OpenCL C (perhaps SPIR also?). Is there someone that has<br>
the "final word" on patches/commits related to OpenCL support, or<br>
volunteering/willing to be one? I think if someone claimed<br>
that responsibility "officially", it would accelerate the<br>
progress towards improved open source OpenCL C support.<br></blockquote><div></div></div><br></div><div class="gmail_extra">A code owner is not just the final word on the subject, but even more than that, it's whomever is interested enough and know who to ask for expert reviews, to progress with a feature, and not let anyone mess up. </div>
<div class="gmail_extra"><br></div><div class="gmail_extra">In light of that, if you care enough about it, and don't mind being included in patch proposals and merge requests, or spending a little extra time reviewing patches or bugging the right people to do so, I think you could easily be the code owner for OpenCL.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">My tuppence.</div><div class="gmail_extra"><br></div><div class="gmail_extra">cheers,</div><div class="gmail_extra">--renato</div></div>
</div></div>
</body>
</html>