0
代码
代码
Issues
Pull Requests
讨论
Wiki
分析
0
ascend-robotascend-robotfix: lintrunner --all-files --take NEWLINE -a
46819fb6创建于 15 天前历史提交
文件最后提交记录最后更新时间
__init__.py
add FALLBACK_LIST and aten_op_tool, not integrated yet Co-authored-by: jimmycao9929<caohaijun3@huawei.com> # message auto-generated for no-merge-commit merge: !30032 merge v2.7.1-0126 into v2.7.1 [inductor] use FALLBACK_LIST rather than GENERATE_LIST Created-by: jimmycao9929 Commit-by: jimmycao9929 Merged-by: ascend-robot Description: **What type of PR is this?** > /kind feature **What does this PR do / why do we need it**: Currently, GENERATE_LIST is adopted to lowering, which is kind of white_list. This mechanism shows a number of problems. Especially, we can not figure out clearly how many aten/prims are fallbacked by us more than native pytorch. Thus, instead of that, we plan to use FALLBACK_LIST. Then we can add op item to this list if some problems (e.g., compile, precision, performance, etc.) with it; and remove it after problems are fixed. **Which issue(s) this PR fixes**: Fixes # **Special notes for your reviewers**: Currently, we only use it for A5 and control with environment switch. After verified carefully, we will remove the env switch. See merge request: Ascend/pytorch!300323 个月前
aten_op_tool.py
add FALLBACK_LIST and aten_op_tool, not integrated yet Co-authored-by: jimmycao9929<caohaijun3@huawei.com> # message auto-generated for no-merge-commit merge: !30032 merge v2.7.1-0126 into v2.7.1 [inductor] use FALLBACK_LIST rather than GENERATE_LIST Created-by: jimmycao9929 Commit-by: jimmycao9929 Merged-by: ascend-robot Description: **What type of PR is this?** > /kind feature **What does this PR do / why do we need it**: Currently, GENERATE_LIST is adopted to lowering, which is kind of white_list. This mechanism shows a number of problems. Especially, we can not figure out clearly how many aten/prims are fallbacked by us more than native pytorch. Thus, instead of that, we plan to use FALLBACK_LIST. Then we can add op item to this list if some problems (e.g., compile, precision, performance, etc.) with it; and remove it after problems are fixed. **Which issue(s) this PR fixes**: Fixes # **Special notes for your reviewers**: Currently, we only use it for A5 and control with environment switch. After verified carefully, we will remove the env switch. See merge request: Ascend/pytorch!300323 个月前
fallback_list_tool.py
fix: lintrunner --all-files --take NEWLINE -a Co-authored-by: huangjingwei<huangjingwei4@huawei.com> # message auto-generated for no-merge-commit merge: !35871 merge v2.7.1_lintrunner into v2.7.1 fix: lintrunner --all-files --take NEWLINE -a Created-by: huangjingwei Commit-by: huangjingwei Merged-by: ascend-robot Description: <!-- PR描述模板更新日期：20260203 --> # 【合入来源】 > <font color="red">**如有社区issue，请关联issue链接**</font>\ > <font color="red">**请勿携带内部流程信息（需求链接、问题单、内部issue等）**</font> - [ ] 需求 - [ ] 问题单 - [x] issue/工单 - [ ] 重构优化 - [ ] 资料更新 # 【修改方案】 > 请描述修改内容的具体实现，涉及哪些组件之间进行交互，可以用1、2、3、...进行罗列\ > 如果是需求或者重构类的PR，需要补充详细设计文档（说明上下游组件关系、时序图、类图、DFX能力等内容） # 【资料变更】 > 请确认是否涉及资料变更。如涉及，需要在PR中体现，并简要说明修改内容。如不涉及，需填写“不涉及” # 【接口变更】 > 请确认是否涉及跨代码仓或者客户面可见的接口变更。如涉及，需要详细说明接口以及对应的变更内容，同时需要在资料中体现。如不涉及，需填写“不涉及” # 【功能验证】 > 说明测试场景，测试方法。如果本次测试方式与常规单元测试不同，请详细说明您的测试步骤\ > 新增/变更内容是否已新增/适配UT测试用例看护，并补充测试自验证截图 # 【CheckList】 > PR提交人对以下CheckList自检项进行全量自检，自检通过或不涉及，均修改 [ ] 为 [x] - [x] 代码注释完备，正确记录错误日志 - [x] 代码实现进行了返回值、空指针等校验 - [x] PR标题正确使用类型标签，如：feat、fix、refactor、docs、test等 - [x] PR持续集成流水线（CI）执行通过，代码检查无异常 See merge request: Ascend/pytorch!3587115 天前