search for: _zl21__nvvm_reflect_anchorv

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

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

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

Hey Jingyue, Though I tried `opt -nvvm-reflect` on both bc files, the nvvm reflect anchor didn't go away; ptxas is still complaining about the duplicate definition of of function '_ZL21__nvvm_reflect_anchorv' . Did I misused the nvvm-reflect pass? Thanks! yuanfeng On Fri, Mar 11, 2016 at 10:10 AM, Jingyue Wu <jingyue at google.com> wrote: > According to the examples you sent, I believe the linking issue was caused > by nvvm reflection anchors. I haven't played with that, but I g...

...eng Peng < > yuanfeng.jack.peng at gmail.com> wrote: > >> Hey Jingyue, >> >> Though I tried `opt -nvvm-reflect` on both bc files, the nvvm reflect >> anchor didn't go away; ptxas is still complaining about the duplicate >> definition of of function '_ZL21__nvvm_reflect_anchorv' . Did I misused >> the nvvm-reflect pass? >> >> Thanks! >> yuanfeng >> >> On Fri, Mar 11, 2016 at 10:10 AM, Jingyue Wu <jingyue at google.com> wrote: >> >>> According to the examples you sent, I believe the linking issue was >>&gt...

...om> wrote: >>> >>>> Hey Jingyue, >>>> >>>> Though I tried `opt -nvvm-reflect` on both bc files, the nvvm reflect >>>> anchor didn't go away; ptxas is still complaining about the duplicate >>>> definition of of function '_ZL21__nvvm_reflect_anchorv' . Did I misused >>>> the nvvm-reflect pass? >>>> >>>> Thanks! >>>> yuanfeng >>>> >>>> On Fri, Mar 11, 2016 at 10:10 AM, Jingyue Wu <jingyue at google.com> >>>> wrote: >>>> >>>>&gt...

It's hard to tell what is wrong without a concrete example. E.g., what is the program you are instrumenting? What is the definition of the hook function? How did you link that definition with the binary? One thing suspicious to me is that you may have linked the definition of _Cool_MemRead_Hook as a host function instead of a device function. AFAIK, PTX assembly cannot be linked. So, if you