[Openmp-dev] Declare variant + Nvidia Device Offload

[Lukas Sommer via Openmp-dev]

Ok, so dollar-sign should work on all architectures and I will create a
patch for that.

Best,

Lukas

Lukas Sommer, M.Sc.
TU Darmstadt
Embedded Systems and Applications Group (ESA)
Hochschulstr. 10, 64289 Darmstadt, Germany
Phone: +49 6151 1622429
www.esa.informatik.tu-darmstadt.de

On 21.05.20 07:31, Johannes Doerfert wrote:
>
> Function names only, yes.
>
> Basically, if "$" as part of a function name is OK in the Intel pipeline.
>
> We will use that to mangle declare variant functions because the "."
> we used so far upsets nvcc...
>
>
> On 5/20/20 8:52 PM, Narayanaswamy, Ravi wrote:
>> I was not following this thread.
>> Is this for function names only?
>> I believe if it is function names only should be ok.
>> Thanks
>> Ravi
>>
>> From: Jon Chesterfield <jonathanchesterfield at gmail.com>
>> Sent: Wednesday, May 20, 2020 4:10 PM
>> To: Johannes Doerfert <johannesdoerfert at gmail.com>
>> Cc: Lukas Sommer <sommer at esa.tu-darmstadt.de>; Jonas Hahnfeld <hahnjo at hahnjo.de>; openmp-dev at lists.llvm.org; Narayanaswamy, Ravi <ravi.narayanaswamy at intel.com>
>> Subject: Re: [Openmp-dev] Declare variant + Nvidia Device Offload
>>
>>> _$_ seems like a reasonable solution, as ISO C/C++ forbids dollar-sign
>> I CC'ed Ravi and Jon to confirm that Intel and AMD toolchains will be
>> be fine with "$" in the symbol name. We already know it should work for
>> NVIDIA and NEC. I guess that would be all.
>>
>> '$' works fine on amdgcn. We're using llvm-mc for the assembler and (nearly?) standard elf for the binary formats so it should work really. Hello world style test passes too.
>>
>> Embedded \0 in the middle of the symbol name was rejected in IR but anything else seems to work.
>>
>> Thanks!
>>
>> Jon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/openmp-dev/attachments/20200521/8ba5d6c6/attachment.html>