Linker issue GPU Coder generated static lib to g++ project.

Question

Markus Walser 2019-10-4

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/483563-linker-issue-gpu-coder-generated-static-lib-to-g-project

评论： Markus Walser 2019-11-21

Hi

I generated a static libxyz.a with the GPU Coder on a Jetson Xavier target. Now I want to link this library into an existing g++ project.

Unfortunately I get unresolved symbols which directs to MathWorks methods like __cudaRegisterLinkedBinary_54_tmpxft_000031a2_00000000_6_MWTargetNetworkImpl_cpp1_ii_beb7

An internet search pointed me to a build example for such use case: https://docs.nvidia.com/cuda/cuda-compiler-driver-nvcc/index.html#examples

There's an intermediate linker step (--device-link) used before generating the static library, in this case libgpu.a:

nvcc --gpu-architecture=sm_50 --device-c a.cu b.cu
nvcc --gpu-architecture=sm_50 --device-link a.o b.o --output-file link.o
nvcc --lib --output-file libgpu.a a.o b.o link.o
g++ host.o --library=gpu --library-path=<path> \
    --library=cudadevrt --library=cudart

Unfortunately I cannot find this --device-link step in the GPU Coders build log before the static library is linked from the object files.

Is there an coder option to enable such device-linker step? Or how could such unresolved symbold be resolved otherwise?