llvm-project/mlir
Alex Zinenko b5756fdaa1 Factor out translation registry.
The mlir-translate tool is expected to discover individual translations at link
time.  These translations must register themselves and may need the utilities
that are currently defined in mlir-translate.cpp for their entry point
functions.  Since mlir-translate is linking against individual translations,
the translations cannot link against mlir-translate themselves.  Extract out
the utilities into a separate "Translation" library to avoid the potential
dependency cycle.  Individual translations link to that library to access
TranslateRegistration. The mlir-translate tool links to individual translations
and to the "Translation" library because it needs the utilities as well.

The main header of the new library is located in include/mlir/Translation.h to
make it easily accessible by translators.  The rationale for putting it to
include/mlir rather than to one of its subdirectories is that its purpose is
similar to that of include/mlir/Pass.h so it makes sense to put them at the
same level.

PiperOrigin-RevId: 222398617
2019-03-29 14:06:19 -07:00
..
g3doc Update 'return' statement syntax in LangRef to reflect the actual parsing syntax. 2019-03-29 14:01:48 -07:00
include/mlir Factor out translation registry. 2019-03-29 14:06:19 -07:00
lib Factor out translation registry. 2019-03-29 14:06:19 -07:00
test Add verifier check for integer constants to check that the value can fit within the type bit width. 2019-03-29 14:05:48 -07:00
tools Factor out translation registry. 2019-03-29 14:06:19 -07:00
utils Rename affineint type to index type. The name 'index' may not be perfect, but is better than the old name. Here is some justification: 2019-03-29 13:24:16 -07:00
.clang-format [mlir] add .clang-format 2019-03-29 12:41:43 -07:00
LICENSE.TXT Continue sketching out basic infrastructure, including an input and output 2019-03-29 12:23:51 -07:00