llvm
/
torch-mlir
mirror of https://github.com/llvm/torch-mlir
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
torch-mlir/frontends/pytorch/test/node_import
History
Sean Silva 7b6fa27838 Rename tests to match the code they test 
- `module_import -> ivalue_import`, as it mainly tests ivalue_importer.cpp
- `graph_import -> node_import`, as it mainly tests node_importer.cpp
 - graph_importer.cpp does call into node_importer.cpp, but doesn't do
 much.

This was getting pretty confusing. Also add README.md's in each
directory for more clarity.
 		2021-02-25 13:31:33 -08:00
..
README.md Rename tests to match the code they test 2021-02-25 13:31:33 -08:00
add3.py Rename tests to match the code they test 2021-02-25 13:31:33 -08:00
debug-info.py Rename tests to match the code they test 2021-02-25 13:31:33 -08:00
elif.py Rename tests to match the code they test 2021-02-25 13:31:33 -08:00
errors.py Rename tests to match the code they test 2021-02-25 13:31:33 -08:00
if.py Rename tests to match the code they test 2021-02-25 13:31:33 -08:00
list.py Rename tests to match the code they test 2021-02-25 13:31:33 -08:00
tuple.py Rename tests to match the code they test 2021-02-25 13:31:33 -08:00
types-bool.py Rename tests to match the code they test 2021-02-25 13:31:33 -08:00
types-none.py Rename tests to match the code they test 2021-02-25 13:31:33 -08:00

README.md

node_import

Most of the tests in this directory test the importing of TorchScript torch::jit::Graph's.

However, TorchScript graphs don't really correspond directly to anything on the MLIR side. They are a weird combination of a context, builder, and function and just holds a torch::jit::Block. It is torch::jit::Node and torch::jit::Block which form the recursive structure analogous to MLIR's operation/region/block.

  • torch::jit::Node == mlir::Operation,
  • torch::jit::Block == mlir::Region containing single mlir::Block

Hence the name of this directory and the corresponding code in node_importer.h/cpp.