main

文件	最后提交记录	最后更新时间
configs	Handle pytorch pybind11 changes and bump nightly pins (#4352) I think this is the simplest approach, for now, to resolve https://github.com/llvm/torch-mlir/issues/4343 It would be good to eventually finish https://github.com/llvm/torch-mlir/pull/4348 ; however, it became a bit too much to rework the generated sources scripts in a timely fashion. See also another parallel attempt to address the ci problems: #4345 This PR modifies the Cmake pytorch configure function to simply not set any TORCH_CXX_FLAGS whenever pytorch is missing the old PYBIND_BUILD_ABI tag. I think whatever compiler flags we were pushing through to make pybind think we are GCC and to use a specific ABI version is just completely unnecessary now. I was worried we might need to update our pybind version in the requirements, but it appears to not be relevant. Additionally, nightly pins are updated and small fixes are made to resolve misc failures in tests after the bump. --------- Signed-off-by: zjgarvey <zjgarvey@gmail.com>	9 个月前
debug	[NFC reformat] Applies pre-commit formatting to Python files. (#3244) This is a large change because prior to this point, Python files in the project were not consistently formatted. This reformats them all with black defaults. Based on experience with prior projects, if you have a dev/long-term branch with Python patches, you can minimize merge conflicts prior to rebasing to include this commit by running black on your modified Python files, squashing, and then rebasing/merging.	2 年前
linalg_on_tensors_backends	Integrate LLVM at 41f65666f6378bba7266be7c662c70074f04ed75 (#4358)	9 个月前
stablehlo_backends	e2e: Enable generate-runtime-verification pass (#3615) This adds the generate-runtime-verification pass into the linalg refbackend, and moves all tests that now abort at runtime into the crash set, sorted by their respective errors. I have fixed on set of errors found that way, which are mismatches between the static dimensions we cast to and the actual dynamic dimensions. This was caused by wrong annotations on the test cases, like in https://github.com/llvm/torch-mlir/pull/3615/files#diff-48bfbf41fcad5fa01b49197d251114f84a2b8de4f1d87ab938a061aedd1419b1R1931	1 年前
test_suite	[Torch] Canonicalize pool ops with single int tuple params. (#4250) Fixes https://github.com/llvm/torch-mlir/issues/3885 by repeating the single int to match with expected spatial dims.	8 个月前
tosa_backends	[TOSA] Add transposed conv support (#4360)	8 个月前
CMakeLists.txt	Re-organize project structure to separate PyTorch dependencies from core project. (#2542) This is a first step towards the structure we discussed here: https://gist.github.com/stellaraccident/931b068aaf7fa56f34069426740ebf20 There are two primary goals: 1. Separate the core project (C++ dialects and conversions) from the hard PyTorch dependencies. We move all such things into projects/pt1 as a starting point since they are presently entangled with PT1-era APIs. Additional work can be done to disentangle components from that (specifically LTC is identified as likely ultimately living in a projects/ltc). 2. Create space for native PyTorch2 Dynamo-based infra to be upstreamed without needing to co-exist with the original TorchScript path. Very little changes in this path with respect to build layering or options. These can be updated in a followup without commingling directory structure changes. This also takes steps toward a couple of other layering enhancements: * Removes the llvm-external-projects/torch-mlir-dialects sub-project, collapsing it into the main tree. * Audits and fixes up the core C++ build to account for issues found while moving things. This is just an opportunistic pass through but roughly ~halves the number of build actions for the project from the high 4000's to the low 2000's. It deviates from the discussed plan by having a projects/ tree instead of compat/. As I was thinking about it, this will better accommodate the follow-on code movement. Once things are roughly in place and the CI passing, followups will focus on more in-situ fixes and cleanups.	2 年前
__init__.py	Re-organize project structure to separate PyTorch dependencies from core project. (#2542) This is a first step towards the structure we discussed here: https://gist.github.com/stellaraccident/931b068aaf7fa56f34069426740ebf20 There are two primary goals: 1. Separate the core project (C++ dialects and conversions) from the hard PyTorch dependencies. We move all such things into projects/pt1 as a starting point since they are presently entangled with PT1-era APIs. Additional work can be done to disentangle components from that (specifically LTC is identified as likely ultimately living in a projects/ltc). 2. Create space for native PyTorch2 Dynamo-based infra to be upstreamed without needing to co-exist with the original TorchScript path. Very little changes in this path with respect to build layering or options. These can be updated in a followup without commingling directory structure changes. This also takes steps toward a couple of other layering enhancements: * Removes the llvm-external-projects/torch-mlir-dialects sub-project, collapsing it into the main tree. * Audits and fixes up the core C++ build to account for issues found while moving things. This is just an opportunistic pass through but roughly ~halves the number of build actions for the project from the high 4000's to the low 2000's. It deviates from the discussed plan by having a projects/ tree instead of compat/. As I was thinking about it, this will better accommodate the follow-on code movement. Once things are roughly in place and the CI passing, followups will focus on more in-situ fixes and cleanups.	2 年前
annotations.py	[NFC reformat] Applies pre-commit formatting to Python files. (#3244) This is a large change because prior to this point, Python files in the project were not consistently formatted. This reformats them all with black defaults. Based on experience with prior projects, if you have a dev/long-term branch with Python patches, you can minimize merge conflicts prior to rebasing to include this commit by running black on your modified Python files, squashing, and then rebasing/merging.	2 年前
framework.py	Add per-test timeouts to catch infinite loops (#3650) Previously we only had full suite timeouts, making it impossible to identify which specific tests were hanging. This patch adds: 1. Per-test timeout support in the test framework 2. A default 600s timeout for all tests 3. A deliberately slow test to verify the timeout mechanism works The timeout is implemented using Python's signal module. Tests that exceed their timeout are marked as failures with an appropriate error message. This should help catch and isolate problematic tests that enter infinite loops, without needing to re-run the entire suite multiple times.	1 年前
registry.py	Add per-test timeouts to catch infinite loops (#3650) Previously we only had full suite timeouts, making it impossible to identify which specific tests were hanging. This patch adds: 1. Per-test timeout support in the test framework 2. A default 600s timeout for all tests 3. A deliberately slow test to verify the timeout mechanism works The timeout is implemented using Python's signal module. Tests that exceed their timeout are marked as failures with an appropriate error message. This should help catch and isolate problematic tests that enter infinite loops, without needing to re-run the entire suite multiple times.	1 年前
reporting.py	[NFC reformat] Applies pre-commit formatting to Python files. (#3244) This is a large change because prior to this point, Python files in the project were not consistently formatted. This reformats them all with black defaults. Based on experience with prior projects, if you have a dev/long-term branch with Python patches, you can minimize merge conflicts prior to rebasing to include this commit by running black on your modified Python files, squashing, and then rebasing/merging.	2 年前
utils.py	[Torch] Extract TensorPlaceholder to a common interface (#3668)	1 年前