-
Notifications
You must be signed in to change notification settings - Fork 24.7k
Enable Direct Use of Arm Compute Library (ACL) in ATen #148542
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
ACL is already built with PyTorch as a shared library when USE_MKLDNN_ACL is set. Currently, it is only used indirectly in ATen via oneDNN for AArch64 targets. However there are cases where it makes sense to utilize ACL directly without oneDNN as an intermediary - e.g. quantization. See pytorch#145942, pytorch#147337, pytorch#146620. This patch enables such use cases by exposing ACL to ATen
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/148542
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 99e5d35 with merge base 6c3492b ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
@pytorchbot label "module: arm" |
@pytorchbot label "ciflow/linux-aarch64" |
@pytorchbot label "topic: not user facing" |
@malfet, @digantdesai This PR contains all the cmake-related changes needed to enable the direct ACL path in ATen in these PRs: #145942, #147337, #146620. |
@pytorchbot label "arm priority" |
ACL is already built with PyTorch as a shared library when USE_MKLDNN_ACL is set.
Currently, it is only used indirectly in ATen via oneDNN for AArch64 targets. However there are cases where it makes sense to utilize ACL directly without oneDNN as an intermediary - e.g. quantization. See #145942, #147337, #146620.
This patch enables such use cases by exposing ACL to ATen
Fixes #ISSUE_NUMBER
cc @jgong5 @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10 @malfet @snadampal @milpuz01