llvm/mlir/unittests/CMakeLists.txt

add_custom_target(MLIRUnitTests)
set_target_properties(MLIRUnitTests PROPERTIES FOLDER "MLIR Tests")

function(add_mlir_unittest test_dirname)
  add_unittest(MLIRUnitTests ${test_dirname} ${ARGN})
endfunction()

add_subdirectory(Dialect)
add_subdirectory(IR)
add_subdirectory(Pass)
add_subdirectory(TableGen)
Add build files and update README. * Add initial version of build files; * Update README with instructions to download and build MLIR from github; -- PiperOrigin-RevId: 241102092 2019-03-30 06:10:12 +01:00			`add_custom_target(MLIRUnitTests)`
			`set_target_properties(MLIRUnitTests PROPERTIES FOLDER "MLIR Tests")`

			`function(add_mlir_unittest test_dirname)`
			`add_unittest(MLIRUnitTests ${test_dirname} ${ARGN})`
			`endfunction()`

			`add_subdirectory(Dialect)`
			`add_subdirectory(IR)`
			`add_subdirectory(Pass)`
[TableGen] Better support for predicate and rewrite rule specification Currently predicates are written with positional placeholders `{N}` and rely on `formatv` as the engine to do substitution. The problem with this approach is that the definitions of those positional placeholders are not consistent; they are entirely up to the defining predicate of question. For example, `{0}` in various attribute constraints is used to mean the attribute, while it is used to main the builder for certain attribute transformations. This can become very confusing. This CL introduces `tgfmt` as a new mechanism to better support for predicate and rewrite rule specification. Instead of entirely relying on positional placeholders, `tgfmt` support both positional and special placeholders. The former is used for DAG operands. The latter, including $_builder, $_op, $_self, are used as special "hooks" to entities in the context. With this, the predicate and rewrite rules specification can be more consistent is more readable. -- PiperOrigin-RevId: 243249671 2019-04-12 14:57:50 +02:00			`add_subdirectory(TableGen)`