mirror of https://github.com/llvm/torch-mlir
README: Move Project Communication section higher
People might want to lurk on discord, and not even check out the code yet.pull/406/head
parent
18e8806b14
commit
a75ae82530
11
README.md
11
README.md
|
@ -30,6 +30,11 @@ We have few paths to lower down to the Torch MLIR Dialect.
|
|||
This path provides the upcoming LTC path of capture. It is based of an unstable devel branch but is the closest way for you to adapt any existing torch_xla derivatives.
|
||||
- “ACAP” - Deprecated torch_xla based capture Mentioned here for completeness.
|
||||
|
||||
## Project Communication
|
||||
|
||||
- `#torch-mlir` channel on the LLVM [Discord](https://discord.gg/xS7Z362) - this is the most active communication channel
|
||||
- Github issues [here](https://github.com/llvm/torch-mlir/issues)
|
||||
- [`torch-mlir` section](https://llvm.discourse.group/c/projects-that-want-to-become-official-llvm-projects/torch-mlir/41) of LLVM Discourse
|
||||
|
||||
## Check out the code
|
||||
|
||||
|
@ -173,12 +178,6 @@ file in the workspace folder with the correct PYTHONPATH set. This allows
|
|||
tools like VSCode to work by default for debugging. This file can also be
|
||||
manually `source`'d in a shell.
|
||||
|
||||
## Project Communication
|
||||
|
||||
- `#torch-mlir` channel on the LLVM [Discord](https://discord.gg/xS7Z362)
|
||||
- Issues [here](https://github.com/llvm/torch-mlir/issues)
|
||||
- [`torch-mlir` section](https://llvm.discourse.group/c/projects-that-want-to-become-official-llvm-projects/torch-mlir/41) of LLVM Discourse
|
||||
|
||||
## Build Python Packages
|
||||
|
||||
We have preliminary support for building Python packages. This can be done
|
||||
|
|
Loading…
Reference in New Issue