pypto/docs/zh/guide/programming_guide/pro/development · CANN/pypto

cann-robotdocs(pypto_pro): Document SK early-start API (SkCap, wait/set) and the superkernel example

文件	最后提交记录	最后更新时间
compilation_and_execution	docs(pypto_pro): Document SK early-start API (SkCap, wait/set) and the superkernel example Co-authored-by: z_noahor<zhouqinghe1@huawei.com> # message auto-generated for no-merge-commit merge: !7258 merge sk_1020_docs into master docs(pypto_pro): Document SK early-start API (SkCap, wait/set) and the superkernel example Created-by: z_noahor Commit-by: z_noahor Merged-by: cann-robot Description: ## 描述 SK 早启相关文档，代码变更见 !7275。 See merge request: cann/pypto!7258	1 天前
tiling	docs: convert Pro documentation figures to editable SVG Co-authored-by: gcw_bTlukKC6<xuxinlei1@huawei.com> # message auto-generated for no-merge-commit merge: !7162 merge newbranch into master docs: convert Pro documentation figures to editable SVG Created-by: gcw_bTlukKC6 Commit-by: gcw_bTlukKC6 Merged-by: cann-robot Description: PR 应该避免没有描述信息，描述信息的最重要的作用是描述修改意图，应该清晰明了。例如：标题中包含了 `fix` 标签，如果没有描述信息，就需要Review人员猜测PR具体修复了哪些内容，或者怀疑修改的必要性。如果PR和特定的Issue相关，可以单独包含一行 `Related Issue:` 放到描述信息最后。下面是一个典型的PR描述信息: `The origin issue template brings too many noise, it's not suitable for git message. eg: comments are not removed, labels are redundant as the PR tile already contains the tag. The guide gives a clear suggestion on how to write the PR body. Related Issue: #1234,#5678` 更多描述信息见：[Commit Message 规范](../docs/zh/contribute/pull-request.md#commit-message) See merge request: cann/pypto!7162	5 天前
vector_computation	fix docs about compact=1 Co-authored-by: ChenYongji123<chenyongji6@huawei.com> # message auto-generated for no-merge-commit merge: !7261 merge master into master fix docs about compact=1 Created-by: ChenYongji123 Commit-by: ChenYongji123 Merged-by: cann-robot Description: PR 应该避免没有描述信息，描述信息的最重要的作用是描述修改意图，应该清晰明了。例如：标题中包含了 `fix` 标签，如果没有描述信息，就需要Review人员猜测PR具体修复了哪些内容，或者怀疑修改的必要性。如果PR和特定的Issue相关，可以单独包含一行 `Related Issue:` 放到描述信息最后。下面是一个典型的PR描述信息: `The origin issue template brings too many noise, it's not suitable for git message. eg: comments are not removed, labels are redundant as the PR tile already contains the tag. The guide gives a clear suggestion on how to write the PR body. Related Issue: #1234,#5678` 更多描述信息见：[Commit Message 规范](../docs/zh/contribute/pull-request.md#commit-message) See merge request: cann/pypto!7261	2 天前
cube_computation.md	docs: convert Pro documentation figures to editable SVG Co-authored-by: gcw_bTlukKC6<xuxinlei1@huawei.com> # message auto-generated for no-merge-commit merge: !7162 merge newbranch into master docs: convert Pro documentation figures to editable SVG Created-by: gcw_bTlukKC6 Commit-by: gcw_bTlukKC6 Merged-by: cann-robot Description: PR 应该避免没有描述信息，描述信息的最重要的作用是描述修改意图，应该清晰明了。例如：标题中包含了 `fix` 标签，如果没有描述信息，就需要Review人员猜测PR具体修复了哪些内容，或者怀疑修改的必要性。如果PR和特定的Issue相关，可以单独包含一行 `Related Issue:` 放到描述信息最后。下面是一个典型的PR描述信息: `The origin issue template brings too many noise, it's not suitable for git message. eg: comments are not removed, labels are redundant as the PR tile already contains the tag. The guide gives a clear suggestion on how to write the PR body. Related Issue: #1234,#5678` 更多描述信息见：[Commit Message 规范](../docs/zh/contribute/pull-request.md#commit-message) See merge request: cann/pypto!7162	5 天前
cube_vector_fusion.md	docs(fix): Repair the docs bug Co-authored-by: lyz0328<liyanzhen@huawei.com> # message auto-generated for no-merge-commit merge: !7245 merge master into master docs(fix): Repair the docs bug Created-by: lyz0328 Commit-by: lyz0328 Merged-by: cann-robot Description: ## 修改说明对 `docs/zh/api` 全量文档（718 个 md）做质量自检，并按自检结论修复以下文档问题。所有改动均为行级文本修正，不改变文档结构与章节内容。 ### 产品支持情况与芯片标签 - index_hiascend.md：补登记 3 个缺失文档——`pypto-conv_backward_filter`、SIMT-API 同步控制简介（synchronization_intro）、Warp函数简介（warp_intro），插入位置与各目录 index.md 的 toctree 顺序保持一致 - pypto-conv.md：修复约束说明中 npu 标签 `id4`/`id5` 与产品支持情况章节重复的问题，改为 `id10`/`id11`，保证 id 在文件内唯一 - pypto-get_convbp_filter_tile_shapes.md / pypto-set_convbp_filter_tile_shapes.md / pypto-conv_backward_filter.md：产品型号名标准化——`Ascend 950PR/Ascend 950DT` → `Ascend 950PR&950DT系列产品`、`Atlas A3 训练系列产品/Atlas A3 推理系列产品` → `Atlas A3系列产品`、`Atlas A2 训练系列产品/Atlas A2 推理系列产品` → `Atlas A2系列产品` ### 术语规范 - PyPto → PyPTO：pypto-assemble.md（3 处）、pypto-view.md（1 处） - TileShape 变体统一（tileshape / tile shape / Tile shape → TileShape）：15 个文件、36 处 - 存储单元名称补全（L1/L0A/L0B/L0C 单独使用 → L1 Buffer / L0A Buffer / L0B Buffer / L0C Buffer）：16 个文件、41 处，含 move.md 小节标题 `### L1->L0A/L0B` → `### L1 Buffer->L0A/L0B Buffer`、matmul.md Kirin9050 切分约束段等 ### 参数表规范 - 参数说明表头统一：`\| 参数 \|` → `\| 参数名 \|`，共 319 个文件；仅替换参数说明章节内的表头行，sum.md 约束说明中的数据类型矩阵（`\| 参数 \| dim=0 \| dim=1 \|`）不属于参数表，保持不动 ### 其他 - 批量修改保持各文件原有行尾风格（仓内 CRLF/LF 混合），未引入行尾变化 See merge request: cann/pypto!7245	2 天前
index.md	docs(pypto_pro):Update documents Co-authored-by: gcw_bTlukKC6<xuxinlei1@huawei.com> # message auto-generated for no-merge-commit merge: !6190 merge docs-pro-sync-0902 into master docs(pypto_pro):Update documents Created-by: gcw_bTlukKC6 Commit-by: gcw_bTlukKC6 Merged-by: cann-robot Description: PR 应该避免没有描述信息，描述信息的最重要的作用是描述修改意图，应该清晰明了。例如：标题中包含了 `fix` 标签，如果没有描述信息，就需要Review人员猜测PR具体修复了哪些内容，或者怀疑修改的必要性。如果PR和特定的Issue相关，可以单独包含一行 `Related Issue:` 放到描述信息最后。下面是一个典型的PR描述信息: `The origin issue template brings too many noise, it's not suitable for git message. eg: comments are not removed, labels are redundant as the PR tile already contains the tag. The guide gives a clear suggestion on how to write the PR body. Related Issue: #1234,#5678` 更多描述信息见：[Commit Message 规范](../docs/zh/contribute/pull-request.md#commit-message) See merge request: cann/pypto!6190	1 个月前
kernel_function.md	docs(pypto_pro): Address documentation review comments Co-authored-by: lyy_617<liyuyanjune@163.com> Co-authored-by: gcw_bTlukKC6<xuxinlei1@huawei.com> # message auto-generated for no-merge-commit merge: !6576 merge docs-pro-sync-0902 into master docs(pypto_pro): Address documentation review comments Created-by: gcw_bTlukKC6 Commit-by: lyy_617;gcw_bTlukKC6 Merged-by: cann-robot Description: PR 应该避免没有描述信息，描述信息的最重要的作用是描述修改意图，应该清晰明了。例如：标题中包含了 `fix` 标签，如果没有描述信息，就需要Review人员猜测PR具体修复了哪些内容，或者怀疑修改的必要性。如果PR和特定的Issue相关，可以单独包含一行 `Related Issue:` 放到描述信息最后。下面是一个典型的PR描述信息: `The origin issue template brings too many noise, it's not suitable for git message. eg: comments are not removed, labels are redundant as the PR tile already contains the tag. The guide gives a clear suggestion on how to write the PR body. Related Issue: #1234,#5678` 更多描述信息见：[Commit Message 规范](../docs/zh/contribute/pull-request.md#commit-message) See merge request: cann/pypto!6576	1 个月前
tensor_creation_and_operations.md	feat(pypto_pro)：support GM as cross core buffer Co-authored-by: huanyongben<huanyongben1@hisilicon.com> # message auto-generated for no-merge-commit merge: !6975 merge master into master feat(pypto_pro)：support GM as cross core buffer Created-by: huanyongben Commit-by: huanyongben Merged-by: cann-robot Description: 1、支持GM作为跨核buffer 2、修复部分框架bug See merge request: cann/pypto!6975	13 天前
tile_creation_and_operations.md	fix docs about compact=1 Co-authored-by: ChenYongji123<chenyongji6@huawei.com> # message auto-generated for no-merge-commit merge: !7261 merge master into master fix docs about compact=1 Created-by: ChenYongji123 Commit-by: ChenYongji123 Merged-by: cann-robot Description: PR 应该避免没有描述信息，描述信息的最重要的作用是描述修改意图，应该清晰明了。例如：标题中包含了 `fix` 标签，如果没有描述信息，就需要Review人员猜测PR具体修复了哪些内容，或者怀疑修改的必要性。如果PR和特定的Issue相关，可以单独包含一行 `Related Issue:` 放到描述信息最后。下面是一个典型的PR描述信息: `The origin issue template brings too many noise, it's not suitable for git message. eg: comments are not removed, labels are redundant as the PR tile already contains the tag. The guide gives a clear suggestion on how to write the PR body. Related Issue: #1234,#5678` 更多描述信息见：[Commit Message 规范](../docs/zh/contribute/pull-request.md#commit-message) See merge request: cann/pypto!7261	2 天前