[Libclc-dev] Add additional targets to configure.py

Jeroen Ketema j.ketema at imperial.ac.uk
Wed Feb 12 10:26:48 PST 2014

Hi Tom,

Thanks for your suggestion. This seems to work with minor modifications to our tool chain.

New patch with nvptx— and nvptx64— targets attached.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Add-generic-nvptx-targets.patch
Type: application/octet-stream
Size: 1026 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/libclc-dev/attachments/20140212/66db1da0/attachment-0002.obj>
-------------- next part --------------

On 12 Feb 2014, at 16:57, Jeroen Ketema <j.ketema at imperial.ac.uk> wrote:

> I will test your suggestion below and get back to you.
> Jeroen
> On 12 Feb 2014, at 16:53, Tom Stellard <tom at stellard.net> wrote:
>> On Wed, Feb 12, 2014 at 04:32:37PM +0000, Jeroen Ketema wrote:
>>>>> Please find attached a patch which add two additional nvptx targets to configure.py. Could this patch please be committed by someone with commit access if this looks ok?
>>>> Do these targets require clang 3.5 ?
>>> No they don’t, basically because we work at the bitcode level and do not care about the actual target machine and neither for that reason does clang care for the third part of the target triple. You can stick in any arbitrary string instead of bugle and things will still work, I believe.
>>> Do you see a better solution instead of two new targets with bugle in their name? The main objective is to get a version of libclc targeted towards nvptx but without the nvidiacl specific overrides (without having to patch libclc manually every time :-)
>> R600 just leaves the third part of the triple empty: r600--.  Would this
>> work OK for you?  My main concern is that if we add a nvptx--bugle
>> target and then someone else wants to add nvptx--foo, then we'll have
>> two targets that produce identical code.
>> -Tom
> _______________________________________________
> Libclc-dev mailing list
> Libclc-dev at pcc.me.uk
> http://www.pcc.me.uk/cgi-bin/mailman/listinfo/libclc-dev

More information about the Libclc-dev mailing list