The JitRunner library is logically very close to the execution engine,
and shares similar dependencies.
find -name "*.cpp" -exec sed -i "s/Support\/JitRunner/ExecutionEngine\/JitRunner/" "{}" \;
Paths
| Differential D79899
[MLIR] Move JitRunner to live with ExecutionEngine ClosedPublic Authored by stephenneuendorffer on May 13 2020, 12:04 PM.
Details Summary The JitRunner library is logically very close to the execution engine, find -name "*.cpp" -exec sed -i "s/Support\/JitRunner/ExecutionEngine\/JitRunner/" "{}" \;
Diff Detail
Event TimelineThis revision is now accepted and ready to land.May 13 2020, 2:10 PM mehdi_amini added inline comments.
stephenneuendorffer added inline comments.
stephenneuendorffer marked an inline comment as done. Closed by commit rGec44e08940f8: [MLIR] Move JitRunner to live with ExecutionEngine (authored by stephenneuendorffer). · Explain WhyMay 15 2020, 2:43 PM This revision was automatically updated to reflect the committed changes.
Revision Contents
Diff 263815 mlir/include/mlir/ExecutionEngine/JitRunner.h
mlir/include/mlir/Support/JitRunner.h
mlir/lib/ExecutionEngine/CMakeLists.txt
mlir/lib/ExecutionEngine/JitRunner.cpp
mlir/lib/Support/CMakeLists.txt
mlir/tools/mlir-cpu-runner/mlir-cpu-runner.cppmlir/tools/mlir-cuda-runner/mlir-cuda-runner.cpp
mlir/tools/mlir-vulkan-runner/mlir-vulkan-runner.cpp
|
This is off-topic, but this should be documented (the code you deleted had a comment to this end).
Isn't the JIT infra mostly coming from libLLVM.so and so shouldn't be a "big dependency"?