<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle21
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">As an otherwise uninterested party, I’ll say that :<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">.cxxcl/.cppcl<o:p></o:p></p>
<p class="MsoNormal">and<o:p></o:p></p>
<p class="MsoNormal">.clcxx/.clcpp<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Are both about equally as acceptable to me barring prior art here. cxxl or cppl doesn’t seem to make sense to me (as you said below, ‘cl’ stands for ‘compute language’, not ‘C-something-starting-with-L’.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I personally have a slight preference for cxxcl/cppcl for purely aesthetic reasons though.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> cfe-dev <cfe-dev-bounces@lists.llvm.org> <b>On Behalf Of
</b>Anastasia Stulova via cfe-dev<br>
<b>Sent:</b> Tuesday, February 16, 2021 9:13 AM<br>
<b>To:</b> cfe-dev@lists.llvm.org; Andrzej Warzynski <Andrzej.Warzynski@arm.com><br>
<b>Subject:</b> Re: [cfe-dev] [RFC] New file extension for compiling C++ for OpenCL sources<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">I am not aware of non-clang implementations of OpenCL kernel language<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">parsing. There are some forks of clang customizing the default behaviour<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">though. But I am not aware of any customizing that specific functionality.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="98%" align="center">
</div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span style="color:black">From:</span></b><span style="color:black"> cfe-dev <<a href="mailto:cfe-dev-bounces@lists.llvm.org">cfe-dev-bounces@lists.llvm.org</a>> on behalf of Andrzej Warzynski via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a>><br>
<b>Sent:</b> 16 February 2021 16:42<br>
<b>To:</b> <a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a> <<a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a>><br>
<b>Subject:</b> Re: [cfe-dev] [RFC] New file extension for compiling C++ for OpenCL sources</span>
<o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">Is there any prior art? As in, what other compilers do? Or is Clang the
<br>
precursor here?<br>
<br>
-Andrzej<br>
<br>
On 16/02/2021 16:27, MLJ1991 via cfe-dev wrote:<br>
> That seems like a good compromise<br>
> <br>
>> On Feb 16, 2021, at 8:26 AM, Anastasia Stulova <br>
>> <Anastasia.Stulova@arm.com <<a href="mailto:Anastasia.Stulova@arm.com">mailto:Anastasia.Stulova@arm.com</a>>> wrote:<br>
>><br>
>> Thanks! I see, I think .cl was meant to represent Compute Language as <br>
>> in OpenCL, I would somehow find it better if we don't split cl... I <br>
>> think that "cl" indicates more intuitively that it is OpenCL specific <br>
>> file. We could however use cppcl?<br>
>><br>
>> ------------------------------------------------------------------------<br>
>> *From:*MLJ1991 <<a href="mailto:marcusljohnson1991@gmail.com%20%0b">marcusljohnson1991@gmail.com
<br>
</a>>> <<a href="mailto:marcusljohnson1991@gmail.com">mailto:marcusljohnson1991@gmail.com</a>>><br>
>> *Sent:*16 February 2021 16:08<br>
>> *To:*Anastasia Stulova <<a href="mailto:Anastasia.Stulova@arm.com%20%0b">Anastasia.Stulova@arm.com
<br>
</a>>> <<a href="mailto:Anastasia.Stulova@arm.com">mailto:Anastasia.Stulova@arm.com</a>>><br>
>> *Cc:*clang developer list <<a href="mailto:cfe-dev@lists.llvm.org%20%0b">cfe-dev@lists.llvm.org
<br>
</a>>> <<a href="mailto:cfe-dev@lists.llvm.org">mailto:cfe-dev@lists.llvm.org</a>>>; nd <nd@arm.com <<a href="mailto:nd@arm.com">mailto:nd@arm.com</a>>>;
<br>
>> Sven Van Haastregt <<a href="mailto:Sven.VanHaastregt@arm.com%20%0b">Sven.VanHaastregt@arm.com
<br>
</a>>> <<a href="mailto:Sven.VanHaastregt@arm.com">mailto:Sven.VanHaastregt@arm.com</a>>><br>
>> *Subject:*Re: [cfe-dev] [RFC] New file extension for compiling C++ for <br>
>> OpenCL sources<br>
>> I mean, if .cl is the OpenCL C extension, logically the C++ extension <br>
>> should be .cxxl or .cppl<br>
>><br>
>>> On Feb 16, 2021, at 7:41 AM, Anastasia Stulova via cfe-dev <br>
>>> <cfe-dev@lists.llvm.org <<a href="mailto:cfe-dev@lists.llvm.org">mailto:cfe-dev@lists.llvm.org</a>>> wrote:<br>
>>><br>
>>> Hello,<br>
>>><br>
>>> Up to now, we have used the same file extension for OpenCL C and C++ <br>
>>> for OpenCL<br>
>>> (<a href="https://clang.llvm.org/docs/UsersManual.html#cxx-for-opencl">https://clang.llvm.org/docs/UsersManual.html#cxx-for-opencl</a>
<br>
>>> <<a href="https://clang.llvm.org/docs/UsersManual.html#cxx-for-opencl">https://clang.llvm.org/docs/UsersManual.html#cxx-for-opencl</a>>). But
<br>
>>> to keep<br>
>>> consistency with the clang driver interface, it makes more sense that <br>
>>> C++ for OpenCL<br>
>>> has a different extension from OpenCL C. Mirroring C and C++ it would <br>
>>> be logical to<br>
>>> support the following:<br>
>>><br>
>>> .cl - OpenCL C source file<br>
>>> .clcpp - C++ for OpenCL source file<br>
>>><br>
>>> I would like to share the review that adds a new file extension for <br>
>>> C++ for OpenCL with<br>
>>> a wider audiencehttps://reviews.llvm.org/D96771 <br>
>>> <<a href="https://reviews.llvm.org/D96771">https://reviews.llvm.org/D96771</a>>. Feel free to provide us any feedback<br>
>>> regarding the direction or implementation details.<br>
>>><br>
>>> Kind regards,<br>
>>> Anastasia<br>
>>> _______________________________________________<br>
>>> cfe-dev mailing list<br>
>>> <a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a> <<a href="mailto:cfe-dev@lists.llvm.org">mailto:cfe-dev@lists.llvm.org</a>><br>
>>> <a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev">https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a>
<br>
>>> <<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev">https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a>><br>
> <br>
> <br>
> _______________________________________________<br>
> cfe-dev mailing list<br>
> <a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a><br>
> <a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev">https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br>
> <br>
_______________________________________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev">https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>