Skip to content

Commit 0a456b7

Browse files
authored
Update README.md with status
1 parent ec93c97 commit 0a456b7

File tree

1 file changed

+9
-7
lines changed

1 file changed

+9
-7
lines changed

README.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -38,12 +38,14 @@ It should be fine to have schedule descriptions, aggregation transforms and pass
3838

3939
This project should have the same initial purpose as the LLVM Test Suite [https://github.com/llvm/llvm-test-suite], but for MLIR.
4040

41-
### How To Run Tests
41+
## Current Status
4242

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.
4445

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

Comments
 (0)