Pull Request已成功合入, 合并人@CANN-robot
（感谢 bianque 的贡献）
Hi @bianque, welcome to submitting your first PR to CANN!
PR Merge Steps
1. CLA Signing
If the current PR label includes cann-cla/yes, it means you have signed the CLA and can proceed to the next step. If the label includes cann-cla/no, please sign the CLA first. If you have any questions, please refer to the FAQ.
2. CI Check
Please comment /compile to trigger the CI pipeline check. If the CI run is successful, the PR will be tagged with ci-pipeline-passed and you can proceed to the next step. If the CI run fails, the PR will be tagged with ci-pipeline-failed, please check the CI logs to fix the issues in the PR. If you have any questions, please refer to the FAQ.
3. Code Review
After CI passes, please refer to the PR Approval Progress and proactively @ the committers in the table to review the code. After approval, committers will comment /lgtm and /approve. Once the lgtm and approved labels are successfully added, the PR will be merged automatically.
Thanks for your pull-request.
The full list of commands accepted by me can be found at here.
You can get sig-info at here.
You can self-configure the PR merge rules for this repository. For more details, please refer to Here.
For more, you also can visit HICANN.
PR Approval Progress
✅ Congratulations! All modules have met the lgtm and approve requirements.
Module Approval Details
| module | lgtm status | approve status |
|---|---|---|
| repo-cann/cannbot-knowledge | ✅ wangsj0012, qq_41667743 (2/2) | ✅ wangsj0012 (1/1) |
💡 Tip:
- Committer can comment
/approveor/lgtm- Commenting
/approveimplies both code review (lgtm) and intent to merge (approve)
CLA Signature Pass
bianque, thanks for your pull request. All authors of the commits have signed the CLA. 👍
/approve
Pull Request 说明
变更说明
关联 Issue：#66
主要改动：
knowledge/contrib/ascendc/runbooks/performance/kernel_clock_and_time_stamp_measurement.md：说明clock与asc_time_stamp的测量边界；去掉输出后重建无干扰基线，不以非零或稳定差值作为唯一判据。knowledge/contrib/ascendc/runbooks/runtime/kernel_asc_dump_data_untrusted_diagnosis.md：按地址空间、模板类型、元素数量、起始地址核对观测通道；区分对齐数据估算、每核总量、SIMD 单次和 VF 单条约束。knowledge/contrib/ascendc/runbooks/runtime/kernel_assert_and_trap_failure_diagnosis.md：区分assert/ascendc_assert与__trap；核对算子失败是否归属目标断言，避免把可选消息缺失误判为断言未触发。knowledge/contrib/ascendc/runbooks/runtime/kernel_debug_api_platform_mode_matrix.md：按症状、目标平台和编程模式路由接口，并按具体接口适用性检查调试开关。knowledge/contrib/ascendc/runbooks/runtime/kernel_printf_no_output_diagnosis.md：排查平台/模式、头文件、dump 开关、容量、执行路径五类原因，以短字符串复验并注明入图配置边界。knowledge/runtime/runbooks/runtime/aicpu_debug_interface_boundaries.md：整理 AI CPUassert、printf、DataStoreBarrier的调用、预算和写可见性边界；读侧组合只作为来源示例。knowledge/contrib/ascendc/index.md、knowledge/contrib/ascendc/runbooks/index.md、性能与运行时索引，以及knowledge/runtime对应索引；更新logs/2026-10-27.md。未包含的范围：未修改
governance/、.agents/skills/、evals/、knowledge/ops/ascendc/{apis,guides}/或既有知识卡。补充说明：
create。六张卡保留 Runbook 路径，通过相邻卡链接区分诊断与接口事实；不扩展到其他技术或平台。asc-devkit固定提交e680c34c09ba6919b3cebd2b7ec027f4ff6f0f22下.agent/skills/ascendc-api-kernel-debug/references/与SKILL.md；AI CPU 卡使用 Registry 登记的cann-docs-raw/asc-devkit/docs/zh/...来源路径。变更类型
验证