torch-mlir

Commit Graph

Author	SHA1	Message	Date
Sean Silva	b2077738ca	Bump llvm-project to 444822d77a7fea28aa49edf24533c987efa1b2ee Fixes: - renames StandardTypes -> BuiltinTypes - std.extract_element -> tensor.extract	2020-12-11 14:43:38 -08:00
Sean Silva	7edb5f3641	[RefBackend] Rename RefBackend dialect to Refback I now realize that VerboseCamelCase is not the best choice for dialect directory/file names and C++ identifiers (take e.g. "Linalg", "Basicpy", etc. as prior art here; not LinearAlgebra or BasicPython). If I had to name the convention it seems to be "Shortword" (or of course just acronym dialects like LLVM, SCF, etc.). This rename also has the side benefit of differentiating RefBackend directories, which now refer to the actual backend itself, from Refback/Refbackrt, which are the dialects which happen to be used by that backend.	2020-10-08 09:07:00 -07:00

Author

SHA1

Message

Date

Sean Silva

b2077738ca

Bump llvm-project to 444822d77a7fea28aa49edf24533c987efa1b2ee

Fixes:
- renames StandardTypes -> BuiltinTypes
- std.extract_element -> tensor.extract

2020-12-11 14:43:38 -08:00

Sean Silva

7edb5f3641

[RefBackend] Rename RefBackend dialect to Refback

I now realize that VerboseCamelCase is not the best choice for dialect
directory/file names and C++ identifiers (take e.g. "Linalg", "Basicpy",
etc. as prior art here; not LinearAlgebra or BasicPython). If I had to
name the convention it seems to be "Shortword" (or of course just
acronym dialects like LLVM, SCF, etc.).

This rename also has the side benefit of differentiating RefBackend
directories, which now refer to the actual backend itself, from
Refback/Refbackrt, which are the dialects which happen to be used by
that backend.

2020-10-08 09:07:00 -07:00

2 Commits (5f1b2ba3232181551cbe3c31b72c409de0d64bf4)