Skip to content

docs: a pack's .onnx component may need vendor op domains, and only ort_run (not 1bit ort-run) takes --input (Fixes #2000) #2002

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

Closed
bong-water-water-bong wants to merge 1 commit into from
Closed

docs: a pack's .onnx component may need vendor op domains, and only ort_run (not 1bit ort-run) takes --input (Fixes #2000) #2002

Show file tree
Hide file tree
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
16 changes: 16 additions & 0 deletions docs/onnx-pack.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,6 +99,22 @@ model.
| gate/up `1024×3072` | CPU EP | same |
| lm_head `1024×151936` | CPU EP | needs a vocab-blocked kernel (N far past one ELF); leave on the CPU until the FFN set is proven |

### A pack's own `*.onnx` component may be vendor-EP targeted (engine#2000)

"It is ONNX" does not mean "it will run". A 1.9 pack's side components look portable — a clean ONNX
interface, e.g. `vision.onnx` declaring `pixel_values [num_patches,1536] f32` and `image_grid_thw [1,3] i64`
→ `image_features [num_logical_patches,2560] f32` — and still will not load under the plain ONNX Runtime
execution providers:

```
Fatal error: com.ryzenai:DynamicPad(-1) is not a registered function/op
```

`com.ryzenai:*` is a custom domain (`DynamicPad`, `matmul_add_to_sd_gemm`, `mha_to_sd_mha`,
`conv_to_nhwc_conv` in that pack's `*_strategy.yaml`), so there is **no CPU-EP oracle**: the component has
to go through its compiled `partitioned/` form. Before treating a component as a reference, check its
op domains — an `ai.onnx`-only graph is a reference you can run, anything with a vendor domain is not.

## What the pack does not do, deliberately

- **KV cache: opt-in, not the default.** The default export re-runs the whole sequence per step, so its
Expand Down
6 changes: 6 additions & 0 deletions docs/onnx.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -463,6 +463,12 @@ silent fall back cannot be mistaken for a device pass.

## Any graph: `ort-run --input`

> **Two entry points, and only one of them has `--input`** (engine#2000). The arbitrary-graph mode below is
> the standalone `ort_run` binary — build it with `ninja ort_run` (`ninja onebit` does **not** build it), then
> run `build/ort_run …`. The habitual `1bit ort-run` subcommand does not accept `--input`, `--output` or
> `--dump-all` and answers `onebit-ort-run: unknown argument --input`. If a build that looks complete has no
> `build/ort_run`, that is why.

`ort-run` speaks two interfaces. With `--ids` it is the Qwen3 language model of
[Qwen3-0.6B](#qwen3-06b) below. With `--input` it is **any** ONNX graph: nothing about the graph's
names, shapes or roles is assumed, so a vision model, an audio model and a one-op toy all take the
Expand Down
Loading