search for: __nvvm_reflect_anchor

...#39;s change makes nvvm_reflect_anchor unnecessary. The issue with dots in names generated by llvm still needs to be fixed. On Apr 9, 2016 8:32 AM, "Jingyue Wu" <jingyue at google.com> wrote: > Artem, > > With David's http://reviews.llvm.org/rL265060, do you think > __nvvm_reflect_anchor is still necessary? > > On Fri, Apr 8, 2016 at 9:37 AM, Yuanfeng Peng via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Yeah, '.' is the direct reason for the ptxas failure here. I'm curious, >> however, about what the purpose of nvvm_reflect_anchor...

...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* &...