Skip to content

Commit 2b0a0f6

Browse files
Martin Yuandbort
authored andcommitted
Fix the xnn_executor_runner location (#952)
Summary: Pull Request resolved: #952 Fix the xnn_executor_runner location. Reviewed By: digantdesai Differential Revision: D50329941 fbshipit-source-id: 83603ec7886a223206be50512657deb6a32d6b41
1 parent 33379e4 commit 2b0a0f6

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/source/tutorial-xnnpack-delegate-lowering.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -138,9 +138,9 @@ The generated model file will be named `[model_name]_xnnpack_[qs8/fp32].pte` dep
138138
We will use `buck2` to run the `.pte` file with XNNPACK delegate instructions in it on your host platform. You can follow the instructions here to install [buck2](getting-started-setup.md#building-a-runtime). You can now run it with the prebuilt `xnn_executor_runner` provided in the examples. This will run the model on some sample inputs.
139139

140140
```bash
141-
buck2 run examples/backend:xnn_executor_runner -- --model_path ./mv2_xnnpack_fp32.pte
141+
buck2 run examples/xnnpack:xnn_executor_runner -- --model_path ./mv2_xnnpack_fp32.pte
142142
# or to run the quantized variant
143-
buck2 run examples/backend:xnn_executor_runner -- --model_path ./mv2_xnnpack_qs8.pte
143+
buck2 run examples/xnnpack:xnn_executor_runner -- --model_path ./mv2_xnnpack_qs8.pte
144144
```
145145

146146
## Building and Linking with the XNNPACK Backend

0 commit comments

Comments
 (0)