-
Notifications
You must be signed in to change notification settings - Fork 683
Arm backend: Add dtype check for aten.where in operator support check #14506
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.
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
Conversation
- Previously, aten.where with non-quantized FP inputs can pass the the operator support check in INT profile, get partitioned, and then be removed from the partition due to FP inputs. - This will introduce dependency cycles, an invalid re-entry pattern `partition -> outside -> partition`, to the graph. - Workaround: when aten.where(cond, x, y) has FP x and y in INT profile, only partition if both come from dequantize ops (DQ_OPS). Note this may over-reject cases like `dq -> op1 -> aten.where -> q` that could be partitioned. - Don't partition aten.where with unsupported input dtype in FP profle. Change-Id: I0cef30ffe36eeb6d9c8fae7618649292df242887 Signed-off-by: Yufeng Shi <yufeng.shi@arm.com>
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/14506
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 New FailuresAs of commit 62a1cb4 with merge base ab31007 ( NEW FAILURES - The following jobs have failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
Arm oobt fail is unrelated and will be fixed by another PR |
@pytorchbot cherry-pick --onto release/1.0 -c regression |
…#14506) - Previously, aten.where with non-quantized FP inputs can pass the the operator support check in INT profile, get partitioned, and then be removed from the partition due to FP inputs. - This will introduce dependency cycles, an invalid re-entry pattern `partition -> outside -> partition`, to the graph. - Workaround: when aten.where(cond, x, y) has FP x and y in INT profile, only partition if both come from dequantize ops (DQ_OPS). Note this may over-reject cases like `dq -> op1 -> aten.where -> q` that could be partitioned. - Don't partition aten.where with unsupported input dtype in FP profle. Signed-off-by: Yufeng Shi <yufeng.shi@arm.com> (cherry picked from commit df5bfd5)
Cherry picking #14506The cherry pick PR is at #14539 and it is recommended to link a regression cherry pick PR with an issue. The following tracker issues are updated: Details for Dev Infra teamRaised by workflow job |
Previously, aten.where with non-quantized FP inputs can pass the the operator support check in INT profile, get partitioned, and then be removed from the partition due to FP inputs.
This will introduce dependency cycles, an invalid re-entry pattern
partition -> outside -> partition
, to the graph.Workaround: when aten.where(cond, x, y) has FP x and y in INT profile, only partition if both come from dequantize ops (DQ_OPS). Note this may over-reject cases like
dq -> op1 -> aten.where -> q
that could be partitioned.Don't partition aten.where with unsupported input dtype in FP profle.
Change-Id: I0cef30ffe36eeb6d9c8fae7618649292df242887
cc @digantdesai @freddan80 @per @zingo @oscarandersson8218