Skip to content

docs(perf): correct CGC input shape compatibility behavior #1438

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Qiong Wu (qiowu) (DingmaomaoBJTU) merged 1 commit into from
Sep 29, 2026
Merged

docs(perf): correct CGC input shape compatibility behavior #1438

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 13 additions & 7 deletions docs/commands/perf.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -424,15 +424,21 @@ not supported.
## Concrete input shapes for CGC

For local ONNX models, Runtime CGC and WinMLCG receive concrete named input
dimensions before compilation. With --input-data, shapes come from NPZ headers
without allocating input tensors. Otherwise, the existing --shape-config and
batch-size resolution rules apply. Rank, static axes, positive dimensions and
shared symbolic names must agree. The source ONNX is not rewritten.
dimensions before compilation. With `--input-data`, shapes come from NPZ headers
(NPY versions 1, 2, and 3) without allocating input tensors. Otherwise, the existing
`--shape-config` and `--batch-size` resolution rules apply. Input names and ranks
must match the ONNX schema, fixed axes must retain their declared extents
(including zero), and shared symbolic names must resolve to the same positive
int64 value. The source ONNX is not rewritten.

Runtime CGC requires a Runtime compiler that supports symbolic-dimension
options. Anonymous dynamic axes are rejected rather than guessed, and these
overrides do not resolve internal data-dependent shapes. Input payload loading
and dtype conversion still occur at the normal input-allocation boundary.
options when named overrides are needed. Anonymous dynamic axes are left
unbound rather than rejected or assigned invented names; the compiler determines
whether they require specialization. This preserves executable graphs with
unused anonymous inputs, but does not add general anonymous-axis binding or
resolve internal data-dependent shapes. Accepting a matching static zero extent
does not guarantee that every CGC operator supports empty tensors. Input payload
loading and dtype conversion still occur at the normal input-allocation boundary.

## See also

Expand Down