351ae0ca55
Some MLIR libraries are intended to be dlopen-ed, but currently all MLIR libraries link against LLVMSupport. After the recent PCH introduction, this causes these libraries to implicitly use the LLVMSupport PCH, which results in the definition of llvm::*ABIBreakingChecks, which results in a ODR violation when loaded with dlopen. Conceptually, libraries that are designed to be dlopen-ed should not simply link against LLVM libraries in non-dylib builds for this reason. (This apparently was a problem before with mlir_apfloat_wrappers.) To fix builds, remove LLVMSupport from runtime libraries that don't need it and, as a workaround, disable PCH for libraries that are in a weird state (use LLVMSupport but happen to not export symbols currently).
29 lines
990 B
CMake
29 lines
990 B
CMake
# Unlike mlir_float16_utils, mlir_c_runner_utils, etc, we do *not* make
|
|
# this a shared library: because doing so causes issues when building
|
|
# on Windows. In particular, various functions take/return `std::vector`
|
|
# but that class is not designed with dllimport/dllexport pragma,
|
|
# therefore it cannot be safely/correctly used across DLL boundaries.
|
|
# Consequently, we avoid using the "mlir_xxx_utils" naming scheme, since
|
|
# that is reserved/intended for shared libraries only.
|
|
add_mlir_library(MLIRSparseTensorRuntime
|
|
File.cpp
|
|
MapRef.cpp
|
|
Storage.cpp
|
|
|
|
EXCLUDE_FROM_LIBMLIR
|
|
|
|
STANDALONE
|
|
)
|
|
mlir_target_link_libraries(MLIRSparseTensorRuntime PUBLIC
|
|
MLIRSparseTensorEnums
|
|
mlir_float16_utils
|
|
)
|
|
set_property(TARGET MLIRSparseTensorRuntime PROPERTY CXX_STANDARD 17)
|
|
|
|
check_cxx_compiler_flag(-Wweak-vtables
|
|
COMPILER_SUPPORTS_WARNING_WEAK_VTABLES)
|
|
if(COMPILER_SUPPORTS_WARNING_WEAK_VTABLES)
|
|
target_compile_options(MLIRSparseTensorRuntime PRIVATE
|
|
"-Wweak-vtables")
|
|
endif()
|