[cfe-dev] [RFC] New file extension for compiling C++ for OpenCL sources

[Keane, Erich via cfe-dev]

As an otherwise uninterested party, I'll say that :

.cxxcl/.cppcl
and
.clcxx/.clcpp

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'.

I personally have a slight preference for cxxcl/cppcl for purely aesthetic reasons though.

From: cfe-dev <cfe-dev-bounces at lists.llvm.org> On Behalf Of Anastasia Stulova via cfe-dev
Sent: Tuesday, February 16, 2021 9:13 AM
To: cfe-dev at lists.llvm.org; Andrzej Warzynski <Andrzej.Warzynski at arm.com>
Subject: Re: [cfe-dev] [RFC] New file extension for compiling C++ for OpenCL sources

I am not aware of non-clang implementations of OpenCL kernel language
parsing. There are some forks of clang customizing the default behaviour
though. But I am not aware of any customizing that specific functionality.


________________________________
From: cfe-dev <cfe-dev-bounces at lists.llvm.org<mailto:cfe-dev-bounces at lists.llvm.org>> on behalf of Andrzej Warzynski via cfe-dev <cfe-dev at lists.llvm.org<mailto:cfe-dev at lists.llvm.org>>
Sent: 16 February 2021 16:42
To: cfe-dev at lists.llvm.org<mailto:cfe-dev at lists.llvm.org> <cfe-dev at lists.llvm.org<mailto:cfe-dev at lists.llvm.org>>
Subject: Re: [cfe-dev] [RFC] New file extension for compiling C++ for OpenCL sources

Is there any prior art? As in, what other compilers do? Or is Clang the
precursor here?

-Andrzej

On 16/02/2021 16:27, MLJ1991 via cfe-dev wrote:
> That seems like a good compromise
>
>> On Feb 16, 2021, at 8:26 AM, Anastasia Stulova
>> <Anastasia.Stulova at arm.com <mailto:Anastasia.Stulova at arm.com>> wrote:
>>
>> Thanks! I see, I think .cl was meant to represent Compute Language as
>> in OpenCL, I would somehow find it better if we don't split cl... I
>> think that "cl" indicates more intuitively that it is OpenCL specific
>> file. We could however use cppcl?
>>
>> ------------------------------------------------------------------------
>> *From:*MLJ1991 <marcusljohnson1991 at gmail.com
<mailto:marcusljohnson1991 at gmail.com%20%0b>>> <mailto:marcusljohnson1991 at gmail.com>>
>> *Sent:*16 February 2021 16:08
>> *To:*Anastasia Stulova <Anastasia.Stulova at arm.com
<mailto:Anastasia.Stulova at arm.com%20%0b>>> <mailto:Anastasia.Stulova at arm.com>>
>> *Cc:*clang developer list <cfe-dev at lists.llvm.org
<mailto:cfe-dev at lists.llvm.org%20%0b>>> <mailto:cfe-dev at lists.llvm.org>>; nd <nd at arm.com <mailto:nd at arm.com>>;
>> Sven Van Haastregt <Sven.VanHaastregt at arm.com
<mailto:Sven.VanHaastregt at arm.com%20%0b>>> <mailto:Sven.VanHaastregt at arm.com>>
>> *Subject:*Re: [cfe-dev] [RFC] New file extension for compiling C++ for
>> OpenCL sources
>> I mean, if .cl is the OpenCL C extension, logically the C++ extension
>> should be .cxxl or .cppl
>>
>>> On Feb 16, 2021, at 7:41 AM, Anastasia Stulova via cfe-dev
>>> <cfe-dev at lists.llvm.org <mailto:cfe-dev at lists.llvm.org>> wrote:
>>>
>>> Hello,
>>>
>>> Up to now, we have used the same file extension for OpenCL C and C++
>>> for OpenCL
>>> (https://clang.llvm.org/docs/UsersManual.html#cxx-for-opencl
>>> <https://clang.llvm.org/docs/UsersManual.html#cxx-for-opencl>). But
>>> to keep
>>> consistency with the clang driver interface, it makes more sense that
>>> C++ for OpenCL
>>> has a different extension from OpenCL C. Mirroring C and C++ it would
>>> be logical to
>>> support the following:
>>>
>>> .cl - OpenCL C source file
>>> .clcpp - C++ for OpenCL source file
>>>
>>> I would like to share the review that adds a new file extension for
>>> C++ for OpenCL with
>>> a wider audiencehttps://reviews.llvm.org/D96771
>>> <https://reviews.llvm.org/D96771>. Feel free to provide us any feedback
>>> regarding the direction or implementation details.
>>>
>>> Kind regards,
>>> Anastasia
>>> _______________________________________________
>>> cfe-dev mailing list
>>> cfe-dev at lists.llvm.org<mailto:cfe-dev at lists.llvm.org> <mailto:cfe-dev at lists.llvm.org>
>>> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>>> <https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev>
>
>
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at lists.llvm.org<mailto:cfe-dev at lists.llvm.org>
> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>
_______________________________________________
cfe-dev mailing list
cfe-dev at lists.llvm.org<mailto:cfe-dev at lists.llvm.org>
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20210216/bc3ba0a6/attachment.html>