forked from OSchip/llvm-project
db1c197bf8
Due to the original type system implementation, LLVMDialect in MLIR contains an LLVMContext in which the relevant objects (types, metadata) are created. When an MLIR module using the LLVM dialect (and related intrinsic-based dialects NVVM, ROCDL, AVX512) is converted to LLVM IR, it could only live in the LLVMContext owned by the dialect. The type system no longer relies on the LLVMContext, so this limitation can be removed. Instead, translation functions now take a reference to an LLVMContext in which the LLVM IR module should be constructed. The caller of the translation functions is responsible for ensuring the same LLVMContext is not used concurrently as the translation no longer uses a dialect-wide context lock. As an additional bonus, this change removes the need to recreate the LLVM IR module in a different LLVMContext through printing and parsing back, decreasing the compilation overhead in JIT and GPU-kernel-to-blob passes. Reviewed By: rriddle, mehdi_amini Differential Revision: https://reviews.llvm.org/D85443 |
||
|---|---|---|
| .. | ||
| CMakeLists.txt | ||
| mlir-rocm-runner.cpp | ||
| rocm-runtime-wrappers.cpp | ||