[QST] Replace binaries part of nvidia_cutlass_dsl package
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.5k
- Forks
- 2.1k
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 7
Description
Hi,
Is it possible to use latest llvm/mlir components to replace these shiped with nvidia_cutlass_dsl? I might want to do some modifications on the source code from llvm/mlir and use these built from source code.
Those binaries are listed as folllowing:
- nvidia_cutlass_dsl/lib/libmlir_c_runner_utils.so
- nvidia_cutlass_dsl/lib/libmlir_cuda_runtime.so
- nvidia_cutlass_dsl/lib/libmlir_float16_utils.so
- nvidia_cutlass_dsl/lib/libmlir_runner_utils.so
- nvidia_cutlass_dsl/python_packages/cutlass/_mlir/_mlir_libs/_mlir.cpython-313-x86_64-linux-gnu.so
- nvidia_cutlass_dsl/python_packages/cutlass/_mlir/_mlir_libs/_mlirDialectsGPU.cpython-313-x86_64-linux-gnu.so
- nvidia_cutlass_dsl/python_packages/cutlass/_mlir/_mlir_libs/_mlirDialectsLLVM.cpython-313-x86_64-linux-gnu.so
- nvidia_cutlass_dsl/python_packages/cutlass/_mlir/_mlir_libs/_mlirDialectsNVGPU.cpython-313-x86_64-linux-gnu.so
- nvidia_cutlass_dsl/python_packages/cutlass/_mlir/_mlir_libs/_mlirExecutionEngine.cpython-313-x86_64-linux-gnu.so
- nvidia_cutlass_dsl/python_packages/cutlass/_mlir/_mlir_libs/_mlirGPUPasses.cpython-313-x86_64-linux-gnu.so
Thanks,
Peter Han
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining how the package produces and loads the listed files under nvidia_cutlass_dsl/lib and python_packages/cutlass/_mlir/_mlir_libs. Trace the packaging entry points for these LLVM/MLIR binaries and determine what would be required to use components built from an external source tree. Done means a documented, working path exists for replacing the shipped components while keeping the package usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- build-system, compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100