-
Notifications
You must be signed in to change notification settings - Fork 607
Qualcomm AI Engine Direct - Requantization Mechanism Implementation #2823
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
Qualcomm AI Engine Direct - Requantization Mechanism Implementation #2823
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/2823
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 337fc1c with merge base 81a7e88 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
Hi @cccclai, |
Hey would you mind explaining a bit what does requantization mean and how it's different than mix precision quantization? Does it mean we'll do 8bit quantization first then 16bit (maybe skip the 8bit quantized ops)? |
Hi Chen, |
@cccclai has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
Thank you for the explanation! Is there an example somewhere to show how to do it, maybe a test case? |
Yes. |
@cccclai has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
Hey do you mind rebasing the change? The CI was broken on the base commit and should be fixed now. |
19f4bcb
to
337fc1c
Compare
Thanks for the friendly reminder. I have just rebased. |
@cccclai has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
Summary: