文件最后提交记录最后更新时间
docs(install): modify installation instruction docs 2 个月前
This change adds English version of the documentation Co-authored-by: tsczajkowski<tomasz.czajkowski@huawei.com> # message auto-generated for no-merge-commit merge: !1246 merge feature-english-documentation into main This change adds English version of the documentation Created-by: tsczajkowski_2025 Commit-by: tsczajkowski Merged-by: ascend-robot Description: The core Triton is a small number of people, and we receive many PRs (thank you!). To help us review your code more quickly, **if you are a new contributor (less than 3 PRs merged) we ask that you complete the following tasks and include the filled-out checklist in your PR description.** Complete the following tasks before sending your PR, and replace [ ] with [x] to indicate you have done them. - [x] I am not making a trivial change, such as fixing a typo in a comment. - [x] I have written a PR description following these [rules](https://cbea.ms/git-commit/#why-not-how). - [x] I have run pre-commit run --from-ref origin/main --to-ref HEAD. - Select one of the following. - [ ] I have added tests. - /test for lit tests - /unittest for C++ tests - /python/test for end-to-end tests - [x] This PR does not need a test because this PR deals with documentation only. - Select one of the following. - [X] I have not added any lit tests. - [ ] The lit tests I have added follow these [best practices](https://mlir.llvm.org/getting_started/TestingGuide/#filecheck-best-practices), including the "tests should be minimal" section. (Usually running Python code and using the instructions it generates is not minimal.) See merge request: Ascend/triton-ascend!12463 个月前
feat(performance):Update the performance charts in README.md 2 个月前
docs(install): modify installation instruction docs 2 个月前
This change adds English version of the documentation Co-authored-by: tsczajkowski<tomasz.czajkowski@huawei.com> # message auto-generated for no-merge-commit merge: !1246 merge feature-english-documentation into main This change adds English version of the documentation Created-by: tsczajkowski_2025 Commit-by: tsczajkowski Merged-by: ascend-robot Description: The core Triton is a small number of people, and we receive many PRs (thank you!). To help us review your code more quickly, **if you are a new contributor (less than 3 PRs merged) we ask that you complete the following tasks and include the filled-out checklist in your PR description.** Complete the following tasks before sending your PR, and replace [ ] with [x] to indicate you have done them. - [x] I am not making a trivial change, such as fixing a typo in a comment. - [x] I have written a PR description following these [rules](https://cbea.ms/git-commit/#why-not-how). - [x] I have run pre-commit run --from-ref origin/main --to-ref HEAD. - Select one of the following. - [ ] I have added tests. - /test for lit tests - /unittest for C++ tests - /python/test for end-to-end tests - [x] This PR does not need a test because this PR deals with documentation only. - Select one of the following. - [X] I have not added any lit tests. - [ ] The lit tests I have added follow these [best practices](https://mlir.llvm.org/getting_started/TestingGuide/#filecheck-best-practices), including the "tests should be minimal" section. (Usually running Python code and using the instructions it generates is not minimal.) See merge request: Ascend/triton-ascend!12463 个月前
fix:Fix the infinite loop in isUsedWithCondition caused by nested for-loops Co-authored-by: wangzhanpeng5<wangzhanpeng5@huawei.com> # message auto-generated for no-merge-commit merge: !1480 merge 0330_main_zj_isUsedWithCondition into main fix:Fix the infinite loop in isUsedWithCondition caused by nested for-loops Created-by: wangzhanpeng5 Commit-by: wangzhanpeng5 Merged-by: ascend-robot Description: ## 修复ISSUE [https://gitcode.com/Ascend/triton-ascend/issues/376](https://gitcode.com/Ascend/triton-ascend/issues/376) ## 同步release分支修复PR [https://gitcode.com/Ascend/triton-ascend/pull/1431](https://gitcode.com/Ascend/triton-ascend/pull/1431) ## 问题描述 在编译包含循环且循环体内调用复杂排序算子(如 triton_patch_topk)的 Triton 内核时,编译过程卡在 TTIR → TTADAPTER 转换阶段。通过 GDB 定位,发现死循环发生在 mlir::triton::isUsedWithCondition 递归分析循环内值的依赖关系时,由于缺少 visited 集合,遇到循环依赖(如循环迭代参数在循环体内被反复使用)时导致无限递归,最终栈溢出或超时。 ## 问题原因分析 - isUsedWithCondition 函数递归遍历 Value 的所有使用,当遇到 LoopLikeOpInterface(如 scf.for)时,会继续递归分析循环迭代参数,而这些参数最终又指向循环体内的值,形成循环依赖。 - 原始实现未记录已访问的 Value,导致同一 Value 被重复递归,形成无限递归。 ## 解决方法 为 isUsedWithCondition 引入 llvm::DenseSet<Value> visited 记录已访问的 Value,并在递归开始时检查,若已访问则直接返回 false。加入 visited 集合后,递归遍历时记录已访问的 Value,遇到循环依赖(如循环迭代参数重复出现)时直接返回,从而切断无限递归链,确保函数能在有限步内完成分析。 See merge request: Ascend/triton-ascend!14802 个月前
test(AutoBlockify): add pytest_ut and mlir testcase Co-authored-by: kang-ingu<kang.ingu@huawei.com> # message auto-generated for no-merge-commit merge: !1335 merge test-auto-blockify-v2 into main test(AutoBlockify): add pytest_ut and mlir testcase Created-by: kang-ingu Commit-by: kang-ingu Merged-by: ascend-robot Description: The core Triton is a small number of people, and we receive many PRs (thank you!). To help us review your code more quickly, **if you are a new contributor (less than 3 PRs merged) we ask that you complete the following tasks and include the filled-out checklist in your PR description.** Complete the following tasks before sending your PR, and replace [ ] with [x] to indicate you have done them. - [ ] I am not making a trivial change, such as fixing a typo in a comment. - [ ] I have written a PR description following these [rules](https://cbea.ms/git-commit/#why-not-how). - [ ] I have run pre-commit run --from-ref origin/main --to-ref HEAD. - Select one of the following. - [ ] I have added tests. - /test for lit tests - /unittest for C++ tests - /python/test for end-to-end tests - [ ] This PR does not need a test because FILL THIS IN. - Select one of the following. - [ ] I have not added any lit tests. - [ ] The lit tests I have added follow these [best practices](https://mlir.llvm.org/getting_started/TestingGuide/#filecheck-best-practices), including the "tests should be minimal" section. (Usually running Python code and using the instructions it generates is not minimal.) See merge request: Ascend/triton-ascend!13352 个月前
docs(install): modify installation instruction docs 2 个月前
docs(install): modify installation instruction docs 2 个月前
docs(install): modify installation instruction docs 2 个月前
docs(install): modify installation instruction docs Co-authored-by: 刘风昇<liufengsheng2@huawei.com> # message auto-generated for no-merge-commit merge: !1474 merge docs_readme into main docs(install): modify installation instruction docs Created-by: meloliu12327 Commit-by: 刘风昇 Merged-by: ascend-robot Description: Modify installation instruction docs. The core Triton is a small number of people, and we receive many PRs (thank you!). To help us review your code more quickly, **if you are a new contributor (less than 3 PRs merged) we ask that you complete the following tasks and include the filled-out checklist in your PR description.** Complete the following tasks before sending your PR, and replace [ ] with [x] to indicate you have done them. - [ ] I am not making a trivial change, such as fixing a typo in a comment. - [ ] I have written a PR description following these [rules](https://cbea.ms/git-commit/#why-not-how). - [ ] I have run pre-commit run --from-ref origin/main --to-ref HEAD. - Select one of the following. - [ ] I have added tests. - /test for lit tests - /unittest for C++ tests - /python/test for end-to-end tests - [ ] This PR does not need a test because FILL THIS IN. - Select one of the following. - [ ] I have not added any lit tests. - [ ] The lit tests I have added follow these [best practices](https://mlir.llvm.org/getting_started/TestingGuide/#filecheck-best-practices), including the "tests should be minimal" section. (Usually running Python code and using the instructions it generates is not minimal.) See merge request: Ascend/triton-ascend!14742 个月前
This change adds English version of the documentation Co-authored-by: tsczajkowski<tomasz.czajkowski@huawei.com> # message auto-generated for no-merge-commit merge: !1246 merge feature-english-documentation into main This change adds English version of the documentation Created-by: tsczajkowski_2025 Commit-by: tsczajkowski Merged-by: ascend-robot Description: The core Triton is a small number of people, and we receive many PRs (thank you!). To help us review your code more quickly, **if you are a new contributor (less than 3 PRs merged) we ask that you complete the following tasks and include the filled-out checklist in your PR description.** Complete the following tasks before sending your PR, and replace [ ] with [x] to indicate you have done them. - [x] I am not making a trivial change, such as fixing a typo in a comment. - [x] I have written a PR description following these [rules](https://cbea.ms/git-commit/#why-not-how). - [x] I have run pre-commit run --from-ref origin/main --to-ref HEAD. - Select one of the following. - [ ] I have added tests. - /test for lit tests - /unittest for C++ tests - /python/test for end-to-end tests - [x] This PR does not need a test because this PR deals with documentation only. - Select one of the following. - [X] I have not added any lit tests. - [ ] The lit tests I have added follow these [best practices](https://mlir.llvm.org/getting_started/TestingGuide/#filecheck-best-practices), including the "tests should be minimal" section. (Usually running Python code and using the instructions it generates is not minimal.) See merge request: Ascend/triton-ascend!12463 个月前
This change adds English version of the documentation Co-authored-by: tsczajkowski<tomasz.czajkowski@huawei.com> # message auto-generated for no-merge-commit merge: !1246 merge feature-english-documentation into main This change adds English version of the documentation Created-by: tsczajkowski_2025 Commit-by: tsczajkowski Merged-by: ascend-robot Description: The core Triton is a small number of people, and we receive many PRs (thank you!). To help us review your code more quickly, **if you are a new contributor (less than 3 PRs merged) we ask that you complete the following tasks and include the filled-out checklist in your PR description.** Complete the following tasks before sending your PR, and replace [ ] with [x] to indicate you have done them. - [x] I am not making a trivial change, such as fixing a typo in a comment. - [x] I have written a PR description following these [rules](https://cbea.ms/git-commit/#why-not-how). - [x] I have run pre-commit run --from-ref origin/main --to-ref HEAD. - Select one of the following. - [ ] I have added tests. - /test for lit tests - /unittest for C++ tests - /python/test for end-to-end tests - [x] This PR does not need a test because this PR deals with documentation only. - Select one of the following. - [X] I have not added any lit tests. - [ ] The lit tests I have added follow these [best practices](https://mlir.llvm.org/getting_started/TestingGuide/#filecheck-best-practices), including the "tests should be minimal" section. (Usually running Python code and using the instructions it generates is not minimal.) See merge request: Ascend/triton-ascend!12463 个月前