You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,12 +38,14 @@ It should be fine to have schedule descriptions, aggregation transforms and pass
38
38
39
39
This project should have the same initial purpose as the LLVM Test Suite [https://github.com/llvm/llvm-test-suite], but for MLIR.
40
40
41
-
### How To Run Tests
41
+
##Current Status
42
42
43
-
#### Choose Your Ingress
43
+
Since this is a new project, we're separating the work in branches that will eventually be merged to `main`.
44
+
After the initial period, when we have a reasonable testing infrastructure, we can fork & create pull requests.
44
45
45
-
#### Choose Your Schedules
46
-
47
-
#### Choose Your Target
48
-
49
-
#### Run The Tests
46
+
The planned work is:
47
+
***Ingress**: PyTorch to Linalg extraction on branch [TBD] (note: since `main` already has partial Torch support, this work can continue on `main`).
48
+
***Harness**: Python harness to bind the MLIR tools, dialects and transforms together on branch [harness](https://github.com/llvm/lighthouse/tree/harness).
49
+
***Schedule**: MLIR schedules to combine into pipelines and combination strategy on branch [TBD].
50
+
***Runtime**: Dependencies, tools and environments to run on various hardware on branch [TBD].
51
+
***Build System**: CMake / Bazel magic to check dependencies, track repositories, run CI on branch [TBD].
0 commit comments