Displaying 3 results from an estimated 3 matches for "zl21__nvvm_reflect_anchorv".
Did you mean:
_zl21__nvvm_reflect_anchorv
2016 Apr 07
2
[GPUCC] how to remove _ZL21__nvvm_reflect_anchorv() automatically?
Hi,
I needed to compile a cuda source file (say, a.cu) into IR (a.bc), and then
merge a.bc with another bitcode file (b.bc, compiled from b.cu). So I
used *llvm-link
a.bc b.bc -o c.bc*
However, I noticed that an internal function '* _ZL21__nvvm_reflect_anchorv()
*' is defined in both a.bc & b.bc, and when merging these two files, one of
the two definitions was renamed to '*_ZL21__nvvm_reflect_anchorv.2()*',
and written into c.bc.
Then I did *llc c.bc -o c.s -march=nvptx ; ptxas c.s -o c.o*
However, ptxas would give the following compl...
2016 Apr 08
2
[GPUCC] how to remove _ZL21__nvvm_reflect_anchorv() automatically?
...gt;> Hi,
>>
>> I needed to compile a cuda source file (say, a.cu) into IR (a.bc), and
>> then merge a.bc with another bitcode file (b.bc, compiled from b.cu).
>> So I used *llvm-link a.bc b.bc -o c.bc*
>>
>> However, I noticed that an internal function '* _ZL21__nvvm_reflect_anchorv()
>> *' is defined in both a.bc & b.bc, and when merging these two files, one
>> of the two definitions was renamed to '*_ZL21__nvvm_reflect_anchorv.2()*',
>> and written into c.bc.
>>
>> Then I did *llc c.bc -o c.s -march=nvptx ; ptxas c.s -o c.o*
&g...
2016 Apr 09
2
[GPUCC] how to remove _ZL21__nvvm_reflect_anchorv() automatically?
...needed to compile a cuda source file (say, a.cu) into IR (a.bc), and
>>>> then merge a.bc with another bitcode file (b.bc, compiled from b.cu).
>>>> So I used *llvm-link a.bc b.bc -o c.bc*
>>>>
>>>> However, I noticed that an internal function '* _ZL21__nvvm_reflect_anchorv()
>>>> *' is defined in both a.bc & b.bc, and when merging these two files,
>>>> one of the two definitions was renamed to '
>>>> *_ZL21__nvvm_reflect_anchorv.2()*', and written into c.bc.
>>>>
>>>> Then I did *llc c.bc -...