[FEA]: `cuda-pathfinder` supporting LLVM/LTO bitcode libraries

[benhg]

Is this a duplicate?

• I confirmed there appear to be no duplicate issues for this request and that I agree to the Code of Conduct

Area

cuda.pathfinder

Is your feature request related to a problem? Please describe.

I would like to be able to use cuda-pathfinder to find a bitcode library similar to how we can find headers today.

Describe the solution you'd like

This description is NVSHMEM/NCCL specific, but probably will apply to many other libraries in very similar ways.

NVSHMEM (and soon NCCL) ship bitcode libraries in the lib/ directory (like libnvshmem_device.bc for LLVM-IR). Projects that depend on these files usually either have their consumer pass paths directly, or use Pathlib.

I would like to be able to call cuda_pathfinder.find_bitcode_lib("nvshmem", lib_type=LLVM) or similar. This would return a string with the path, or would potentially return an ObjectCode with that object. I think string path is probably best.

The search order would be similar to that of the .so library search order or the header search order.

Describe alternatives you've considered

As described above, people tend to ask their users to pass the absolute path or roll their own with Pathlib.

Additional context

No response

[sb17v]

Similar to NVSHMEM, the NCCL bitcode library resides in the lib/ directory (libnccl_device.bc for LLVM IR). We would like to get the bitcode library path in similar way by calling cuda_pathfinder.find_bitcode_lib("nccl", lib_type=LLVM) for NCCL.