From cf487f144c66b64cd1105ba5cbed7dc76f16c502 Mon Sep 17 00:00:00 2001 From: Chen Lai Date: Tue, 23 Apr 2024 14:50:51 -0700 Subject: [PATCH] update sdk delegate integration (#3246) Summary: Pull Request resolved: https://github.com/pytorch/executorch/pull/3246 As title Reviewed By: tarun292 Differential Revision: D56479387 fbshipit-source-id: c324d2b46dc7f849dfb42b3452c6a82f24aa9319 --- docs/source/sdk-delegate-integration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/sdk-delegate-integration.md b/docs/source/sdk-delegate-integration.md index 7f8c61af8c..8003371155 100644 --- a/docs/source/sdk-delegate-integration.md +++ b/docs/source/sdk-delegate-integration.md @@ -20,7 +20,7 @@ Delegate authors propagate what transformations occur in a lowered backend by re For example: - **{ 0: (10, 11), 1: (11, 12) }:** Identifiers 0 and 1 in the runtime correspond to operators with the debug handles (10, 11) and (11, 12) respectively. -- **{ “Fancy Fusion”: (11, 12, 15) }**: Identifier “Fancy Fusion” in the runtime corresponds to operators with debug handles (11, 12, 15). +- **{ “fused_op_1_2_3”: (11, 12, 15) }**: Identifier “fused_op_1_2_3” in the runtime corresponds to operators with debug handles (11, 12, 15), and 11, 12, 15 corresponds to the op 1, op 2 and op 3. ```{Note} Identifiers are a means of connecting runtime results to the model graph; the interpretation of the identifiers is defined by the delegate author.