search for: cuda_hook

...s you sent, I believe the linking issue was caused > by nvvm reflection anchors. I haven't played with that, but I guess running > nvvm-reflect on an IR removes the nvvm reflect anchors. After that, you can > llvm-link the two bc/ll files. > > Another potential issue is that your cuda_hooks-sm_30.ll is unoptimized. > This could cause the instrumented code to run super slow. > > On Fri, Mar 11, 2016 at 9:40 AM, Yuanfeng Peng < > yuanfeng.jack.peng at gmail.com> wrote: > >> Hey Jingyue, >> >> Attached are the .ll files. Thanks! >> >>...

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

...was >>> caused by nvvm reflection anchors. I haven't played with that, but I guess >>> running nvvm-reflect on an IR removes the nvvm reflect anchors. After that, >>> you can llvm-link the two bc/ll files. >>> >>> Another potential issue is that your cuda_hooks-sm_30.ll is unoptimized. >>> This could cause the instrumented code to run super slow. >>> >>> On Fri, Mar 11, 2016 at 9:40 AM, Yuanfeng Peng < >>> yuanfeng.jack.peng at gmail.com> wrote: >>> >>>> Hey Jingyue, >>>> >>...

...reflection anchors. I haven't played with that, but I guess >>>>> running nvvm-reflect on an IR removes the nvvm reflect anchors. After that, >>>>> you can llvm-link the two bc/ll files. >>>>> >>>>> Another potential issue is that your cuda_hooks-sm_30.ll is >>>>> unoptimized. This could cause the instrumented code to run super slow. >>>>> >>>>> On Fri, Mar 11, 2016 at 9:40 AM, Yuanfeng Peng < >>>>> yuanfeng.jack.peng at gmail.com> wrote: >>>>> >>>&gt...