.asc and .cce enter the device-source table, and the CANN toolkit turns out to be one download

The Ascend example named an `xim:cann-toolkit` that did not exist and a device
extension the engine did not know. Both are now answerable, and the answer to
the second was simpler than the design doc said.

THE EXTENSION. `.asc` is Ascend C, compiled by `ccec` (BiSheng) from the CANN
toolkit, and `.cce` is the older spelling of the same thing. They belong in the
table for the reason `.sycl` does: the content is ordinary C++ and the
criterion is the compiler. CANN's own operator libraries already split
`op_kernel/` from `op_host/`, and CMake registers ASC as a language of its own
-- the island is a shape Ascend already has, not one mcpp imposes on it.
Adding to this table cannot change a build that works today: device extensions
are absent from the default source glob, and one named in `sources` was until
now a hard error.

THE TOOLKIT. The design doc recorded that the vendor's container image pulls
anonymously, which is true and is not the simplest route -- it stopped one
layer short. Measured today, with no credentials at all: every toolkit from
8.0.RC1 to 8.5.0 is a plain `.run` on Huawei's own OBS, answering 200 to a HEAD
request. 8.5.0 is 1.12 GB for x86_64 and 1.10 GB for aarch64.

It installs without root and without a driver:

    ./Ascend-cann-toolkit_8.5.0_linux-x86_64.run --install \
        --install-path=<dir> --quiet

and 2.9 GB later the two pieces the lane needs are both there:
`x86_64-linux/ccec_compiler/bin/{ccec,bisheng}` runs and reports clang 15.0.5,
and `x86_64-linux/simulator/` carries 38 SoC directories, each with its own
`libpem_davinci.so`. So the whole lane -- compiler and a hardware-free way to
run what it produces -- is one anonymous download.

The installer writes two things outside its install path, `~/Ascend` (8 KB, an
install record) and `~/var/log/ascend_seclog`. Measured: overriding `HOME` for
the duration contains both, and the payload installs identically, so a package
recipe need not be a bad citizen of the user's home directory.

This settles what the design doc listed as the lane's only remaining
prerequisite. Compliance-wise it sits in the first tier of the standing rule --
closed-source and not redistributable, so it is fetched from the vendor's own
URL with no CN mirror, which costs nothing here because the vendor's URL is
already in-country.

Verified after the mcpp-plugins 0.2.2 release: the multi-backend example now
resolves the PUBLISHED `mcpp:plugins@0.2.2` from the index with no path
override and no lock file, and runs -- `backend: cpu` with no accelerator and
`backend: cuda` on a real device.

Author: speak-agent

.agents/docs/2026-09-07-general-build-infrastructure-gaps-design.md

@@ -769,6 +769,32 @@ C6 值得单独说明:它是这批里唯一无法在开发机上验证的判据
 **这一项不是引擎工作量,是判断整套设计对不对的实验。** 它的产出是一份带判据的报告
 加一个规则包(§10.6),不是一个要长期维护的 fork。
 
+## 14b. 昇腾工具包的取得路径(修订八:比修订三所写的更简单)
+
+修订三的结论是"官方镜像可匿名拉取",这仍然成立,但它不是最简的那条路,而当时没有再往下
+找一层。实测(2026-09-07,HEAD 请求,无任何凭据):
+
+| 版本 | `Ascend-cann-toolkit_<ver>_linux-x86_64.run` | 大小 |
+|---|---|---|
+| 8.0.RC1 / 8.0.RC2 / 8.0.0 | 200 | 1.95 / 2.00 / 2.07 GB |
+| 8.1.RC1 | 200 | 2.16 GB |
+| 8.2.RC1 / 8.3.RC1 | 200 | 2.30 / 2.44 GB |
+| 8.5.0 | 200 | 1.12 GB |
+
+URL 形如
+`https://ascend-repo.obs.cn-east-2.myhuaweicloud.com/CANN/CANN%20<ver>/Ascend-cann-toolkit_<ver>_linux-x86_64.run`。
+
+这条路径把 `xim:cann-toolkit` 从"要在配方里走 docker registry 的 token 握手、拉 10 个层、
+再从层里刨目录"降成"下载一个 `.run`、非交互安装、导出目录" —— 而索引里已有 `.run` 安装
+器的先例(`qemu-user-aarch64`),docker 拉取则一个先例都没有(`openclaw` 里那条是别的
+东西)。**没有先例的机制不是不可以引入,但在有先例的机制够用时引入它是净损失。**
+
+合规上这落在用户既定不变量的第一档:**闭源、不可再分发的东西从厂商自有 URL 直取,不做
+CN 镜像**。厂商 URL 本身就在国内,所以镜像这一层在这里也没有意义。
+
+一个记法上的更正:修订三写的是"毕昇与模拟器在同一个包里,是一个获取问题不是两个"。这仍然
+对,但"那个包"现在指的是这个 `.run`,不是那个镜像。
+
 ## 15. 第二个后端才暴露的五处缺口(修订七)
 
 前十四节的缺口清单来自**读代码**与**一个后端的实践**。写第二个后端的时候,五处新缺口

docs/20-heterogeneous-builds.md

@@ -87,6 +87,7 @@ does not accept C++20 modules.
 |---|---|
 | CUDA, HIP | `.cu`, `.hip` |
 | SYCL | `.sycl` (2026.9.6.1+) |
+| Ascend C | `.asc`, `.cce` (2026.9.6.5+) |
 | GLSL, by stage | `.comp`, `.vert`, `.frag`, `.geom`, `.tesc`, `.tese`, `.mesh`, `.task`, `.rgen`, `.rint`, `.rahit`, `.rchit`, `.rmiss`, `.rcall` |
 | GLSL, stage-less | `.glsl` |
 | HLSL | `.hlsl` |

docs/zh/20-heterogeneous-builds.md

@@ -70,6 +70,7 @@ C++20 modules 的编译器。
 |---|---|
 | CUDA、HIP | `.cu`、`.hip` |
 | SYCL | `.sycl`(2026.9.6.1+) |
+| Ascend C | `.asc`、`.cce`(2026.9.6.5+) |
 | GLSL(按 stage) | `.comp`、`.vert`、`.frag`、`.geom`、`.tesc`、`.tese`、`.mesh`、`.task`、`.rgen`、`.rint`、`.rahit`、`.rchit`、`.rmiss`、`.rcall` |
 | GLSL(无 stage) | `.glsl` |
 | HLSL | `.hlsl` |

modules/source-kind/src/source_kind.cppm

@@ -264,8 +264,15 @@ constexpr std::string_view kHeaderExtensions[] = { ".h", ".hpp", ".hh", ".hxx" }
 // extension, so a rule package refuses a stage-less name — which is the right
 // place for that message, and the reason this table does not need to know
 // which of these extensions name a stage.
+//
+// `.asc` is Ascend C, compiled by `ccec` (BiSheng) from the CANN toolkit. It is
+// here for the reason `.sycl` is: the language is ordinary C++ and the
+// criterion is the compiler. CANN's own operator libraries already split
+// `op_kernel/` from `op_host/`, and CMake registers ASC as a LANGUAGE of its
+// own -- so the island is the shape Ascend already has, not one mcpp imposes.
+// `.cce` is the older spelling of the same thing and is accepted beside it.
 constexpr std::string_view kDeviceExtensions[] = {
-    ".cu", ".hip", ".sycl",
+    ".cu", ".hip", ".sycl", ".asc", ".cce",
     ".comp", ".vert", ".frag", ".geom", ".tesc", ".tese", ".mesh", ".task",
     ".rgen", ".rint", ".rahit", ".rchit", ".rmiss", ".rcall",
     ".glsl", ".hlsl", ".cl", ".metal",