llvm
/
torch-mlir
mirror of https://github.com/llvm/torch-mlir
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
torch-mlir/.gitmodules

7 lines
226 B
Plaintext
Raw Permalink Normal View History

s/external/externals/g (#1222) Fix remaining instances of `external/llvm-project`.
2022-08-13 22:13:56 +08:00
[submodule "externals/llvm-project"]
[NFC] Rename external -> externals (#699)
2022-03-27 00:12:27 +08:00
path = externals/llvm-project
Add llvm-project submodule. * Checked out a084b94f1198df600fff0632ad54fe6121e23943
2020-08-02 05:46:49 +08:00
url = https://github.com/llvm/llvm-project.git
Remove mlir-hlo (replace with stablehlo). (#2460) We just have to do this: I ran into an issue today where I needed to make a one line patch to stablehlo to work around a compiler issue, and it is completely unapparent how to do so given that the mlir-hlo repo is a read-only export and is at the tail end of a multi-week integration chain from the open-source stablehlo repo. We've discussed this often enough and gotten +1 from everyone that they are ok with taking the e2e testing hit if it becomes necessary: It is necessary as the current situation is unmanageable. Looking at it, I expect it wouldn't actually be very difficult to build a little runner binary out of the stablehlo interpreter and subprocess call that in order to get the testing coverage back. I leave that as an exercise to the users of this part of the stack and recommend following the breadcrumbs from the deleted python/torch_mlir_e2e_test/stablehlo_backends/linalg_on_tensors.py file and the main.py changes. Note that I am pointing us at a stablehlo fork for the moment until it is apparent that we don't need to carry any local patches to it. We can update this in a few days if everything is clear.
2023-09-13 10:10:02 +08:00
[submodule "externals/stablehlo"]
path = externals/stablehlo
Revert accidental change to submodule origin. (#2477)
2023-09-20 14:05:52 +08:00
url = https://github.com/openxla/stablehlo.git