0
代码
代码
Issues
Pull Requests
讨论
Wiki
分析
0
Bboes129Fit 06-fused-attention.py for the lastest triton-ascend
dfb3439d创建于 27 天前历史提交
文件最后提交记录最后更新时间
01-vector-add.py
fix(docs&driver): migrate dockerfile and tutorials, and fix allocate_workspace Co-authored-by: zhang-chunli01<zhangchunli19@huawei.com> # message auto-generated for no-merge-commit merge: !1091 merge migrate-docs into main fix(docs&driver): migrate dockerfile and tutorials, and fix allocate_workspace Created-by: zhang-chunli01 Commit-by: zhang-chunli01 Merged-by: ascend-robot Description: ## 描述 <!--在这里详细描述你的改动，包括改动的原因和所采取的方法。--> ## checklist <!-- [x] 表示选中 --> - [ ] 是否通过本地IDE对代码进行静态检查 - [ ] 是否通过本地IDE对代码进行格式化处理 - [ ] 是否进行空指针校验 - [ ] 是否进行返回值校验 - [ ] 是否正确释放new/malloc申请的内存 - [ ] 是否充分考虑接口的异常场景 - [ ] 是否正确记录错误日志 See merge request: Ascend/triton-ascend!10914 个月前
02-fused-softmax.py
fix(docs&driver): migrate dockerfile and tutorials, and fix allocate_workspace Co-authored-by: zhang-chunli01<zhangchunli19@huawei.com> # message auto-generated for no-merge-commit merge: !1091 merge migrate-docs into main fix(docs&driver): migrate dockerfile and tutorials, and fix allocate_workspace Created-by: zhang-chunli01 Commit-by: zhang-chunli01 Merged-by: ascend-robot Description: ## 描述 <!--在这里详细描述你的改动，包括改动的原因和所采取的方法。--> ## checklist <!-- [x] 表示选中 --> - [ ] 是否通过本地IDE对代码进行静态检查 - [ ] 是否通过本地IDE对代码进行格式化处理 - [ ] 是否进行空指针校验 - [ ] 是否进行返回值校验 - [ ] 是否正确释放new/malloc申请的内存 - [ ] 是否充分考虑接口的异常场景 - [ ] 是否正确记录错误日志 See merge request: Ascend/triton-ascend!10914 个月前
03-matrix-multiplication.py
test(tutorials): move test cases in tutorials to pytest_ut, move examples to unitest Co-authored-by: jeshd<chengmaofan@huawei.com> # message auto-generated for no-merge-commit merge: !1644 merge cases_refactor_for_main into main test(tutorials): move test cases in tutorials to pytest_ut, move examples to unitest Created-by: jeshd Commit-by: jeshd 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. --> ### Related Issue https://gitcode.com/Ascend/triton-ascend/issues/396 ### Summary This PR mainly organizes the examples in the Ascend tutorial into pytest cases, and migrates the original examples to unittest. ### Changes Added test cases for low-memory dropout, extern functions, grouped gemm, persistent matmul, etc. Meanwhile, converted the corresponding test cases under the tutorial directory to pytest format, keeping them consistent with the original tutorial examples. Fixed test failures in fused-softmax, matrix-multiplication, demo-libentry, rab_time, hstu_attention and other test cases. For each test script name.py in third_party/ascend/tutorials, there is a corresponding pytest test case script test_name.py in third_party/ascend/unittest/pytest_ut. - [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 fix test cases. - 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!16441 个月前
04-low-memory-dropout.py
test(tutorials): move test cases in tutorials to pytest_ut, move examples to unitest Co-authored-by: jeshd<chengmaofan@huawei.com> # message auto-generated for no-merge-commit merge: !1644 merge cases_refactor_for_main into main test(tutorials): move test cases in tutorials to pytest_ut, move examples to unitest Created-by: jeshd Commit-by: jeshd 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. --> ### Related Issue https://gitcode.com/Ascend/triton-ascend/issues/396 ### Summary This PR mainly organizes the examples in the Ascend tutorial into pytest cases, and migrates the original examples to unittest. ### Changes Added test cases for low-memory dropout, extern functions, grouped gemm, persistent matmul, etc. Meanwhile, converted the corresponding test cases under the tutorial directory to pytest format, keeping them consistent with the original tutorial examples. Fixed test failures in fused-softmax, matrix-multiplication, demo-libentry, rab_time, hstu_attention and other test cases. For each test script name.py in third_party/ascend/tutorials, there is a corresponding pytest test case script test_name.py in third_party/ascend/unittest/pytest_ut. - [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 fix test cases. - 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!16441 个月前
05-layer-norm.py
test(tutorials): move test cases in tutorials to pytest_ut, move examples to unitest Co-authored-by: jeshd<chengmaofan@huawei.com> # message auto-generated for no-merge-commit merge: !1644 merge cases_refactor_for_main into main test(tutorials): move test cases in tutorials to pytest_ut, move examples to unitest Created-by: jeshd Commit-by: jeshd 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. --> ### Related Issue https://gitcode.com/Ascend/triton-ascend/issues/396 ### Summary This PR mainly organizes the examples in the Ascend tutorial into pytest cases, and migrates the original examples to unittest. ### Changes Added test cases for low-memory dropout, extern functions, grouped gemm, persistent matmul, etc. Meanwhile, converted the corresponding test cases under the tutorial directory to pytest format, keeping them consistent with the original tutorial examples. Fixed test failures in fused-softmax, matrix-multiplication, demo-libentry, rab_time, hstu_attention and other test cases. For each test script name.py in third_party/ascend/tutorials, there is a corresponding pytest test case script test_name.py in third_party/ascend/unittest/pytest_ut. - [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 fix test cases. - 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!16441 个月前
06-fused-attention.py
Fit 06-fused-attention.py for the lastest triton-ascend 当前最新版本的triton-ascend版本已经不再支持triton.language.extra.cann.extension>，示例代码中import triton.language.extra.cann.extension as extension会报错 解决方案： 移除import triton.language.extra.cann.extension as extension 替换extension.extract_slice和extension.insert_slice为tl.extract_slice让示例脚本可以正常运行 27 天前
07-extern-functions.py
test(tutorials): move test cases in tutorials to pytest_ut, move examples to unitest Co-authored-by: jeshd<chengmaofan@huawei.com> # message auto-generated for no-merge-commit merge: !1644 merge cases_refactor_for_main into main test(tutorials): move test cases in tutorials to pytest_ut, move examples to unitest Created-by: jeshd Commit-by: jeshd 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. --> ### Related Issue https://gitcode.com/Ascend/triton-ascend/issues/396 ### Summary This PR mainly organizes the examples in the Ascend tutorial into pytest cases, and migrates the original examples to unittest. ### Changes Added test cases for low-memory dropout, extern functions, grouped gemm, persistent matmul, etc. Meanwhile, converted the corresponding test cases under the tutorial directory to pytest format, keeping them consistent with the original tutorial examples. Fixed test failures in fused-softmax, matrix-multiplication, demo-libentry, rab_time, hstu_attention and other test cases. For each test script name.py in third_party/ascend/tutorials, there is a corresponding pytest test case script test_name.py in third_party/ascend/unittest/pytest_ut. - [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 fix test cases. - 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!16441 个月前
08-grouped-gemm.py
test(tutorials): move test cases in tutorials to pytest_ut, move examples to unitest Co-authored-by: jeshd<chengmaofan@huawei.com> # message auto-generated for no-merge-commit merge: !1644 merge cases_refactor_for_main into main test(tutorials): move test cases in tutorials to pytest_ut, move examples to unitest Created-by: jeshd Commit-by: jeshd 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. --> ### Related Issue https://gitcode.com/Ascend/triton-ascend/issues/396 ### Summary This PR mainly organizes the examples in the Ascend tutorial into pytest cases, and migrates the original examples to unittest. ### Changes Added test cases for low-memory dropout, extern functions, grouped gemm, persistent matmul, etc. Meanwhile, converted the corresponding test cases under the tutorial directory to pytest format, keeping them consistent with the original tutorial examples. Fixed test failures in fused-softmax, matrix-multiplication, demo-libentry, rab_time, hstu_attention and other test cases. For each test script name.py in third_party/ascend/tutorials, there is a corresponding pytest test case script test_name.py in third_party/ascend/unittest/pytest_ut. - [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 fix test cases. - 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!16441 个月前
09-persistent-matmul.py
test(tutorials): move test cases in tutorials to pytest_ut, move examples to unitest Co-authored-by: jeshd<chengmaofan@huawei.com> # message auto-generated for no-merge-commit merge: !1644 merge cases_refactor_for_main into main test(tutorials): move test cases in tutorials to pytest_ut, move examples to unitest Created-by: jeshd Commit-by: jeshd 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. --> ### Related Issue https://gitcode.com/Ascend/triton-ascend/issues/396 ### Summary This PR mainly organizes the examples in the Ascend tutorial into pytest cases, and migrates the original examples to unittest. ### Changes Added test cases for low-memory dropout, extern functions, grouped gemm, persistent matmul, etc. Meanwhile, converted the corresponding test cases under the tutorial directory to pytest format, keeping them consistent with the original tutorial examples. Fixed test failures in fused-softmax, matrix-multiplication, demo-libentry, rab_time, hstu_attention and other test cases. For each test script name.py in third_party/ascend/tutorials, there is a corresponding pytest test case script test_name.py in third_party/ascend/unittest/pytest_ut. - [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 fix test cases. - 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!16441 个月前