Displaying 4 results from an estimated 4 matches for "inst_axpy".
2016 Mar 12
2
instrumenting device code with gpucc
...ely the reason for my issue.
>>>>
>>>> So I did the following as you suggested(axpy-sm_30.bc is the
>>>> instrumented bitcode, and cuda_hooks-sm_30.bc contains the hook functions):
>>>>
>>>> *llvm-link axpy-sm_30.bc cuda_hooks-sm_30.bc -o inst_axpy-sm_30.bc*
>>>>
>>>> *llc inst_axpy-sm_30.bc -o axpy-sm_30.s*
>>>>
>>>> *"/usr/local/cuda/bin/ptxas" "-m64" "-O3" -c "--gpu-name" "sm_30"
>>>> "--output-file" axpy-sm_30.o axpy-sm_...
2016 Mar 10
4
instrumenting device code with gpucc
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
2016 Mar 13
2
instrumenting device code with gpucc
...;>>>
>>>>>> So I did the following as you suggested(axpy-sm_30.bc is the
>>>>>> instrumented bitcode, and cuda_hooks-sm_30.bc contains the hook functions):
>>>>>>
>>>>>> *llvm-link axpy-sm_30.bc cuda_hooks-sm_30.bc -o inst_axpy-sm_30.bc*
>>>>>>
>>>>>> *llc inst_axpy-sm_30.bc -o axpy-sm_30.s*
>>>>>>
>>>>>> *"/usr/local/cuda/bin/ptxas" "-m64" "-O3" -c "--gpu-name" "sm_30"
>>>>>> "-...
2016 Mar 15
2
instrumenting device code with gpucc
...t;>>> So I did the following as you suggested(axpy-sm_30.bc is the
>>>>>>>> instrumented bitcode, and cuda_hooks-sm_30.bc contains the hook functions):
>>>>>>>>
>>>>>>>> *llvm-link axpy-sm_30.bc cuda_hooks-sm_30.bc -o inst_axpy-sm_30.bc*
>>>>>>>>
>>>>>>>> *llc inst_axpy-sm_30.bc -o axpy-sm_30.s*
>>>>>>>>
>>>>>>>> *"/usr/local/cuda/bin/ptxas" "-m64" "-O3" -c "--gpu-name" "sm_30"...