Skip to content

Commit bab910d

Browse files
SPEC-015, the target sets and test archives in docs/21, docs/08 and docs/50, and the release's notes for target sets and the pack model
Co-authored-by: speak-agent <248744407+speak-agent@users.noreply.github.com>
1 parent 772a82d commit bab910d

12 files changed

Lines changed: 252 additions & 3 deletions

‎CHANGELOG.md‎

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,18 @@
88

99
### Added
1010

11+
- **Target sets (SPEC-015).** A `--target` whose first segment is a system
12+
word names every row of the target table with that system and environment:
13+
`openkal` is `x86_64-openkal` and `aarch64-openkal`, `linux-musl` the musl
14+
rows this mcpp builds. Each member is a leg. `build` builds every leg (planned
15+
one after another, built at once); `run` runs the first leg this machine
16+
reaches, its own architecture first; `test` runs the legs it reaches, reports
17+
the others built and not run, and fails when no test ran. The `mcpp.build`
18+
envelope adds `legs`, the events their `triple`; `self env` adds `legs`
19+
(e2e 963). `[build] target` takes one target.
20+
- **Tests built once, run elsewhere.** `mcpp test --no-run --archive <file>`
21+
writes every leg's tests with `mcpp-tests.json`; `mcpp test --archive <file>`
22+
in a checkout runs what this machine reaches and builds nothing (e2e 964).
1123
- **The build's contract, `${mcpp.contract}`.** Every configuration writes
1224
`mcpp-contract.json` beside its compile database: the compiler of each
1325
language with the words every unit is compiled with (target, sysroot,
@@ -28,6 +40,26 @@
2840

2941
### Changed
3042

43+
- **A pack holds the legs it names (SPEC-014 2.0).** `--target
44+
x86_64-openkal` packs that architecture; `--target openkal` packs both into
45+
one tree. The platform no longer widens a pack: `[platform] universal`,
46+
`[pack] universal` and `--no-universal` lose their effect, with a message
47+
that names the new spelling (`[pack] targets = ["openkal"]`; docs/51).
48+
Images of a platform with a runner have one layout whatever the number of
49+
legs: `bin/<name>`, `bin/<name>.exe`, `lib/<arch>/`, and with
50+
`--mode self-contained` `libexec/<runner>/<os>-<arch>/`. The image embedded
51+
in a carrier belongs to `--pkg-format single-file` only. A set of native
52+
programs is a package per leg (e2e 955, 983, 984).
53+
- **The Windows launcher is a program.** `bin/<name>.exe` replaces
54+
`bin/<name>.cmd`: no "Terminate batch job" prompt, and the process is named
55+
after the package. The POSIX launcher hands over to it under Git Bash, MSYS
56+
and Cygwin.
57+
- **`--systems` takes `<os>`, `<os>-<arch>` and `all`, and `[pack] systems`.**
58+
`--pkg-format` takes a list of containers of one staged tree (`tar,okb`),
59+
built once (e2e 985). Single files cover legs × systems (e2e 986).
60+
- **The pack summary names where the package runs.** `Runs on` and one `Not
61+
covered` line per pair the package does not reach; `mcpp.pack` adds
62+
`pkgFormats` and `runsOn`. A tree that runs nowhere is refused.
3163
- **A target reads the descriptor blocks its row names, never the build
3264
machine's (#851).** A target that is not Linux, macOS or Windows read the
3365
block of the system mcpp ran on, so a Web build took a dependency's `linux`

‎docs/08-testing.md‎

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -197,6 +197,24 @@ otherwise, so it needs no `libc++_shared.so` on the device.
197197
The runner itself, named runners, and what a board declares are
198198
[41 — Reaching a Device](41-devices.md).
199199

200+
### Built once, run elsewhere (mcpp 2026.10.30.1+)
201+
202+
An ok image is the same bytes on every system, and a test built for
203+
`x86_64-windows-gnu` on Linux runs on Windows. `--archive` separates the two
204+
halves:
205+
206+
```bash
207+
mcpp test --target openkal --no-run --archive tests.tar.gz # build every leg's tests, write them
208+
mcpp test --archive tests.tar.gz # in a checkout: run what this machine reaches
209+
```
210+
211+
The archive holds each leg's test programs and `mcpp-tests.json`, which names
212+
each test's leg, arguments and working directory. Reading it builds nothing;
213+
the tests run in the checkout, through this machine's runner or system, and the
214+
report is `mcpp test`'s. A failed test exits 1, and so does an archive of which
215+
no test ran. Legs this machine does not reach are reported as not run
216+
([SPEC-015 §4](specs/target-sets.md)).
217+
200218
## Tests that cannot run beside each other
201219

202220
`mcpp test` runs test programs on a worker pool. One board on one probe, one

‎docs/21-the-target-triple.md‎

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -196,6 +196,30 @@ different artefacts. Writing the segment is how that choice is made.
196196
default fill, and `msvc` is a different object ABI rather than a different C
197197
library, so the segment is meaningful there in both systems.
198198

199+
## Target Sets (mcpp 2026.10.30.1+)
200+
201+
A `--target` whose first segment is a system word — `linux`, `macos`,
202+
`windows`, `openkal`, `emscripten`, `ios`, `android`, `none` — names a **target
203+
set**: every row of the target table with that system and environment that
204+
this mcpp builds. The environment is completed as above (`linux` is
205+
`linux-gnu`, `windows` is `windows-gnu`); `none` has no default and is refused.
206+
207+
| Set | Members (2026.10.30.1, openkal-platform 0.18.0) |
208+
|---|---|
209+
| `openkal` | `x86_64-openkal`, `aarch64-openkal` |
210+
| `linux-musl` | `x86_64-linux-musl`, `aarch64-linux-musl` |
211+
| `linux` | `x86_64-linux-gnu`, `aarch64-linux-gnu` |
212+
213+
Every member must select the same platform; a set whose members select
214+
different platforms is refused, and the message lists each member's. A command
215+
acts once per member, each member a **leg**: `build` builds every leg, `run`
216+
runs the first leg this machine reaches (its own architecture first), `test`
217+
runs the legs it reaches and fails when none ran, and `pack` packs the legs
218+
as [10](10-pack-and-release.md) describes. Reports and machine output name the
219+
members, never the set. `[build] target` takes one target; a set belongs on the
220+
command line and in `[pack] targets`. The rules are
221+
[SPEC-015](specs/target-sets.md).
222+
199223
## The Build Report
200224

201225
The report heads with the target as written and resolves it to the compiler's

‎docs/50-machine-output.md‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -949,6 +949,16 @@ A run ended by SIGINT, SIGTERM or SIGHUP leaves `cancelled` in both files
949949
"data":{"result":"/…/target/x86_64-linux-gnu/c0641c458b2bde43/result.json","status":"ok","finishedAt":1792964065954}}
950950
```
951951

952+
**Several legs** *(2026.10.30.1+)*. A command over a target set, or over more
953+
than one `--target`, builds a leg per target ([SPEC-015](specs/target-sets.md)).
954+
Every leg writes its own `result.json`. The `mcpp.build` envelope's `data` is the
955+
first leg's record, its `status` is the legs' together, and `legs` holds every
956+
leg's record; each `artifact` and `diagnostic` event carries the `triple` of its
957+
leg. `.last-result.json` names the first leg's record and adds `legs`, one
958+
`{triple, result, status}` per leg. With one leg the envelope, the events and
959+
both files are as before. `self env --target <set>` adds `legs` to `mcpp.env`,
960+
one report per leg, the top-level fields being the first leg's.
961+
952962
### `mcpp.launch` — the way `mcpp run` starts the program
953963

954964
```

‎docs/README.md‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -176,4 +176,5 @@ downstream tooling.
176176
- [SPEC-011 — Concurrent runs: the build directory lock, whole outputs, optimistic writes, cancellation](specs/concurrency.md)
177177
- [SPEC-012 — Output for people: two streams, two media, the kinds of line, colour](specs/human-output.md)
178178
- [SPEC-013 — Platforms: the configuration of a class of targets, its selection, merge, graph completion, link, seal, runner and carrier](specs/platforms.md)
179-
- [SPEC-014 — Packaging and distribution: link, closure and container, legs, the staged tree, universal and single-file packages](specs/packaging.md)
179+
- [SPEC-014 — Packaging and distribution: link, closure and container, legs, the staged tree, the platform's tree, run coverage and single-file packages](specs/packaging.md)
180+
- [SPEC-015 — Target sets and legs: spelling and expansion, commands over several legs, test archives](specs/target-sets.md)

‎docs/specs/README.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,7 @@
4444
| [SPEC-012](human-output.md) | 面向人的输出:两条流、两种介质、行的种类、颜色 | 评审中 v1.0 | 2026-10-26 | mcpp >= 2026.10.26.1 |
4545
| [SPEC-013](platforms.md) | 平台:`[platform]` 的七组键、版本组与 `hosted`,三种写法与层次,目标图与宿主图的选择,`cfg(platform)`,依赖图的补全,链接、命名与封装,运行器与载体,平台阶段与协议 17 | 评审中 v1.2 | 2026-10-29 | mcpp >= 2026.10.27.1;§10 的执行宿主与 §11 的载体架构 mcpp >= 2026.10.29.1 |
4646
| [SPEC-014](packaging.md) | 打包与分发:链接、闭包、容器三个维度与构建腿,腿的合并,暂存树与 `mcpp-package.json`,平台的树、运行覆盖、单文件、容器列表、签名、压缩、合并与分发描述 | 评审中 v2.0 | 2026-10-30 | mcpp >= 2026.10.30.1;逐条标注 |
47+
| [SPEC-015](target-sets.md) | 目标集合与腿:集合的写法与展开,命令对多条腿的语义,串行规划与一起构建,测试归档,机器输出 | 评审中 v1.0 | 2026-10-30 | mcpp >= 2026.10.30.1 |
4748

4849
## 文档约定
4950

‎docs/specs/packaging.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010
| 对应实现 | mcpp >= 2026.10.30.1 |
1111
| 相关设计文档 | `.agents/docs/2026-10-29-ecosystem-target-sets-packaging-and-editors-design.md`(§4、§13)、`.agents/docs/2026-10-28-platforms-part2-packaging-and-distribution-design.md`(§2–§7、§14)、`.agents/docs/2026-10-28-platforms-design.md`(§4.7)、`.agents/docs/2026-10-29-openkal-run-test-pack-design.md`(§2.2、§2.6) |
1212
| 相关 issue | mcpp#847、mcpp#849、mcpp#860 |
13-
| 相关规范 | [SPEC-007](build-plugins.md)(包格式提供者、artifact action)、[SPEC-011](concurrency.md)(原子发布)、[SPEC-013](platforms.md)(平台、运行器、载体)、SPEC-015(目标集合与腿) |
13+
| 相关规范 | [SPEC-007](build-plugins.md)(包格式提供者、artifact action)、[SPEC-011](concurrency.md)(原子发布)、[SPEC-013](platforms.md)(平台、运行器、载体)、[SPEC-015](target-sets.md)(目标集合与腿) |
1414
| 使用文档 | [10 —— 发布打包](../zh/10-pack-and-release.md) |
1515

1616
用语按 RFC 2119:**必须 / 禁止**为强制,**应当**为建议,**可以**为可选。

‎docs/specs/target-sets.md‎

Lines changed: 120 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,120 @@
1+
# SPEC-015:目标集合与腿
2+
3+
| 项 | 值 |
4+
|---|---|
5+
| 规范编号 | SPEC-015 |
6+
| 标题 | 目标集合与腿:集合的写法与展开,命令对集合的语义,腿的规划与构建,测试归档,机器输出 |
7+
| 状态 | 评审中 v1.0 |
8+
| 版本 | 1.0 |
9+
| 最后修改 | 2026-10-30 |
10+
| 对应实现 | mcpp >= 2026.10.30.1 |
11+
| 相关设计文档 | `.agents/docs/2026-10-29-ecosystem-target-sets-packaging-and-editors-design.md`(§3) |
12+
| 相关 issue | mcpp#847 |
13+
| 相关规范 | [SPEC-011](concurrency.md)(锁与原子发布)、[SPEC-013](platforms.md)(平台的选择、运行器、执行宿主)、[SPEC-014](packaging.md)(打包的腿与合并) |
14+
| 使用文档 | [21 —— 目标三元组](../zh/21-the-target-triple.md)、[08 —— 测试](../zh/08-testing.md)、[50 —— 机器输出](../zh/50-machine-output.md) |
15+
16+
用语按 RFC 2119:**必须 / 禁止**为强制,**应当**为建议,**可以**为可选。
17+
18+
## 0. 范围
19+
20+
本规范规定 `--target` 的一种写法:**目标集合**,即一个系统(及至多一个环境)所含的、本 mcpp 构建的全部目标;以及
21+
`build`、`run`、`test`、`pack`、`self env` 对一组目标(**腿**)的行为。腿的打包与合并属于 SPEC-014 §1.4。
22+
23+
## 1. 写法与展开
24+
25+
### 1.1 集合的识别
26+
27+
- **精确目标**是三元组,含义不变(docs/21)。
28+
- **目标集合**是首段属于系统词表的写法。词表:`linux`、`macos`、`windows`、`openkal`、`emscripten`、`ios`、`android`、
29+
`none`。识别只看首段:`triple::parse` 不校验首段(`unknown-linux-gnu` 解析为架构 `unknown`),所以集合不以解析失败识别。
30+
- 集合由系统与至多一个环境组成:`openkal`、`linux-musl`、`windows-gnu`、`none-eabihf`。多于两段的写法被拒绝。
31+
32+
### 1.2 环境的补全
33+
34+
| 写法 | 系统 | 环境 |
35+
|---|---|---|
36+
| `linux` | linux | `gnu` |
37+
| `linux-<env>` | linux | `<env>` |
38+
| `windows` | windows | `gnu`(不含 `msvc`) |
39+
| `android` | linux | `android`(不接受更多的段) |
40+
| `none` | — | 拒绝:裸机没有缺省环境,写出 `none-elf`、`none-eabi`、`none-eabihf` |
41+
| `none-<env>`、`ios`、`ios-<env>` | 同名 | 按写法 |
42+
| `openkal`、`macos`、`emscripten` | 同名 | 无;写出环境段时被拒绝 |
43+
44+
### 1.3 展开
45+
46+
1. 候选为内置目标表中系统与环境都相同、且等级不是 `planned` 的行。
47+
2. 每个候选按 SPEC-013 的规则选择平台(目标行的平台列、`[target.<sel>] platform`、`MCPP_<T>_PLATFORM`)。全部候选
48+
**必须**选到同一个平台;否则命令被拒绝,消息逐行写出每个候选及其平台。
49+
3. 没有候选时命令被拒绝;表中有 `planned` 的行时,消息写出这些行。
50+
4. 结果为规范三元组,按目标表的顺序。
51+
52+
| 写法 | 展开(mcpp 2026.10.30.1 的目标表与 openkal-platform 0.18.0) |
53+
|---|---|
54+
| `openkal` | `x86_64-openkal`、`aarch64-openkal` |
55+
| `linux-musl` | `x86_64-linux-musl`、`aarch64-linux-musl`(`planned` 的行不在内) |
56+
| `linux` | `x86_64-linux-gnu`、`aarch64-linux-gnu` |
57+
58+
### 1.4 一条命令的腿
59+
60+
- 一条命令的腿是全部 `--target` 的并集:集合展开为其成员,精确目标保持原写法(单独规划时的补全与报告不变)。
61+
- 同一目标只算一次(以规范形式比较)。顺序为目标表的顺序;表中没有的目标排在其后,保持书写的顺序。
62+
- 机器输出与摘要只写展开后的目标;集合的写法不进入记录。
63+
- `[build] target` **必须**是精确目标;写集合时清单被拒绝。集合可以写在命令行与 `[pack] targets`(SPEC-014 §2.2)。
64+
65+
## 2. 命令的语义
66+
67+
| 命令 | 一条腿 | 多条腿 |
68+
|---|---|---|
69+
| `build` | 构建这条腿 | 构建全部腿,每条腿在 `target/<triple>/` 下;一个 `Finished` |
70+
| `run` | 本机架构经运行器;另一架构经执行宿主(SPEC-013 §10),否则拒绝 | 选第一条能到达的腿,本机架构优先;只构建这一条;写出所选的腿;都不能到达时拒绝 |
71+
| `test` | 同 `run` 的到达规则;到达不了即拒绝 | 构建全部腿,运行能到达的腿,其余逐条报告"已构建、未运行"及原因;**一个测试都没有运行时失败**(退出码 1) |
72+
| `pack` | 一个包 | SPEC-014 §1.4 |
73+
| `self env` | 不变 | `data.legs[]` 每项是一份精确目标的报告;顶层取第一条腿 |
74+
75+
平台包中不带 `--target` 的 `mcpp test` 遍历平台的 `targets`,即多条腿的一个特例,行为同上表。
76+
77+
## 3. 规划与构建
78+
79+
- 腿**逐条串行规划**:一次规划一条腿,`mcpp.lock` 只在规划阶段写入,避免 SPEC-011 §4 的乐观写入冲突。
80+
- 规划完成后各腿**一起构建**:`[build] jobs` 按腿静态分摊;构建目录锁按目标名排序获取。
81+
- 一条腿失败时,其余腿完成构建;命令的状态为第一条失败的腿的状态。
82+
- 单腿时规划、构建、`.last-result.json` 与记录的 `configuration` 与 2026.10.29.1 相同。多腿时 `.last-result.json` 记录每条腿,
83+
根目录的编译数据库为第一条腿的。
84+
85+
## 4. 测试归档
86+
87+
- **写**:`mcpp test [--target <t>...] --no-run --archive <file>` 构建各腿的测试程序,与清单 `mcpp-tests.json`(每个测试的腿、
88+
参数、工作目录)一起写为一个 tar 归档。归档是引擎的格式,与平台的容器无关。
89+
- **读**:`mcpp test --archive <file>` 在同一项目的检出中运行归档内本机能到达的测试,不构建;工作目录为项目检出;报告与
90+
`mcpp test` 相同。
91+
- 读取时:有测试失败则退出码 1;一个测试都没有运行则退出码 1 并写明;本机到达不了的腿报告为"未运行"。
92+
- 原生交叉同样适用:在 Linux 上构建的 `x86_64-windows-gnu` 测试可以在 Windows 上运行。
93+
94+
## 5. 机器输出
95+
96+
- `mcpp.build`:单腿时逐字节不变。多腿时 `data` 的顶层字段取第一条腿,`status` 汇总全部腿,`legs[]` 每项为一份完整的结果
97+
记录;`artifact` 与 `diagnostic` 事件带 `triple`。
98+
- `mcpp.env`(`self env --format json`):多腿时增加 `legs[]`。
99+
- `mcpp.pack`:`legs`、`pkgFormats`、`runsOn`(SPEC-014 §9)。
100+
- 新字段只增加,不改变已有字段的含义(docs/50)。
101+
102+
## 6. 判据
103+
104+
1. `mcpp build --target openkal` 构建两条腿,各在 `target/<triple>/` 下,一个 `Finished`;信封的 `data` 为第一条腿的记录,
105+
`legs` 含两条,每个 `artifact` 事件写出其腿(e2e 963)。
106+
2. `mcpp run --target openkal` 运行本机的腿并写出所选的腿;`mcpp test --target openkal` 运行本机的腿,另一条报告为
107+
已构建、未运行,退出码 0(e2e 963)。
108+
3. 各腿都到达不了时 `mcpp test` 不运行任何测试,退出码 1 并写明(e2e 963)。
109+
4. `mcpp self env --target openkal --format json` 报告两条腿(e2e 963)。
110+
5. `none`(无环境)、`linux-msvc`(无成员)与 `[build] target` 中的集合被拒绝(e2e 963)。
111+
6. 集合的识别、补全、展开、去重与顺序,`planned` 的行不在内,候选选到不同平台被拒绝(unit `TargetSet`)。
112+
7. 腿的规划串行、构建一起、作业分摊与第一条失败的腿(unit `BuildLegs`)。
113+
8. `--no-run --archive` 写出的归档含两条腿与清单;在没有 `target/` 的检出中 `--archive` 运行本机的腿、不构建;失败的
114+
测试使退出码为 1;没有一条腿能到达的归档不运行任何测试且退出码为 1(e2e 964)。
115+
116+
## 变更记录
117+
118+
| 版本 | 日期 | 变更 |
119+
|---|---|---|
120+
| 1.0 | 2026-10-30 | 首版(mcpp 2026.10.30.1,设计 2026-10-29 §3):集合的识别、补全与展开,一条命令的腿,`build`、`run`、`test`、`self env` 对多条腿的语义,串行规划与一起构建,测试归档,机器输出;判据 1–8(e2e 963、964,unit `TargetSet`、`BuildLegs`)。 |

‎docs/zh/08-testing.md‎

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -173,6 +173,21 @@ test result ok. 0 passed; 0 failed; 2 built, not run
173173
runner 本身、具名 runner,以及一块板子声明了什么,见
174174
[41 —— 抵达一台设备](41-devices.md)。
175175

176+
### 构建一次,各处运行(mcpp 2026.10.30.1+)
177+
178+
ok 映像在每个系统上是同样的字节;在 Linux 上为 `x86_64-windows-gnu` 构建的测试
179+
在 Windows 上运行。`--archive` 把两半分开:
180+
181+
```bash
182+
mcpp test --target openkal --no-run --archive tests.tar.gz # 构建各腿的测试并写出
183+
mcpp test --archive tests.tar.gz # 在检出中运行本机能到达的部分
184+
```
185+
186+
归档含各腿的测试程序与 `mcpp-tests.json`(每个测试的腿、参数与工作目录)。读取
187+
时不构建;测试在检出中经本机的运行器或系统运行,报告与 `mcpp test` 相同。有测试
188+
失败时退出码为 1,一个测试都没运行的归档也是 1。本机到达不了的腿报告为未运行
189+
([SPEC-015 §4](../specs/target-sets.md))。
190+
176191
## 不能彼此并排运行的测试
177192

178193
`mcpp test` 在一个工作池上运行测试程序。一块接了一个探针的板子、一块 GPU、一个串口,

‎docs/zh/21-the-target-triple.md‎

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -180,6 +180,26 @@ LLVM 23.1.3 与 glibc。`aarch64-linux-musl` 仍是静态 musl 产物的显式
180180
而 `msvc` 是不同的对象 ABI 而非不同的 C 库,因此那一段在两套体系下都
181181
有意义。
182182

183+
## 目标集合(mcpp 2026.10.30.1+)
184+
185+
首段是系统词的 `--target`(`linux`、`macos`、`windows`、`openkal`、`emscripten`、
186+
`ios`、`android`、`none`)是一个**目标集合**:目标表中系统与环境相同、且本
187+
mcpp 构建的全部行。环境按上一节补全(`linux` 即 `linux-gnu`,`windows` 即
188+
`windows-gnu`);`none` 没有缺省环境,被拒绝。
189+
190+
| 集合 | 成员(2026.10.30.1,openkal-platform 0.18.0) |
191+
|---|---|
192+
| `openkal` | `x86_64-openkal`、`aarch64-openkal` |
193+
| `linux-musl` | `x86_64-linux-musl`、`aarch64-linux-musl` |
194+
| `linux` | `x86_64-linux-gnu`、`aarch64-linux-gnu` |
195+
196+
全部成员必须选到同一个平台;成员选到不同平台时命令被拒绝,消息写出每个成员
197+
的平台。命令对每个成员各执行一次,每个成员是一条**腿**:`build` 构建全部腿,
198+
`run` 运行本机能到达的第一条腿(本机架构优先),`test` 运行能到达的腿、一个都
199+
没运行时失败,`pack` 按 [10](10-pack-and-release.md) 打包。报告与机器输出写成员,
200+
不写集合。`[build] target` 只接受一个目标;集合写在命令行与 `[pack] targets`。
201+
规则见 [SPEC-015](../specs/target-sets.md)。
202+
183203
## 构建报告
184204

185205
报告以写下的目标为标题,并把它解析成编译器自己的拼法:

0 commit comments

Comments
 (0)