-
Notifications
You must be signed in to change notification settings - Fork 754
Qualcomm AI Engine Direct -- update documents #4590
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
chiwwang
commented
Aug 8, 2024
- Updated QNN download links.
- Unified setup.md and build-run-qualcomm-ai-engine-direct-backend.md
- Fixed build commands in build-run-qualcomm-ai-engine-direct-backend.md
1. Updated QNN download links. 2. Unified setup.md and build-run-qualcomm-ai-engine-direct-backend.md 3. Fixed build commands in build-run-qualcomm-ai-engine-direct-backend.md
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/4590
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit dbb452f with merge base 2405f74 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
cccclai
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for updating the documents! Just some minor comments. Should we add a session for x86 simulator? I find it super helpful. And possibly a model supported list.
| cp schema/program.fbs exir/_serialize/program.fbs | ||
| cp schema/scalar_type.fbs exir/_serialize/scalar_type.fbs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we good with this now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No. But this action is more related to AOT compilation, so I moved there:
https://github.com/pytorch/executorch/pull/4590/files#diff-8bac58bd3ddef654a20549948dfea5d27f76a8ee29544328f65819cc0ccd7bcfR205
| mkdir build_x86_64 | ||
| cd build_x86_64 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's add them to git ignore?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine with that... but how about using the name already in .gitignore?
cmake-out/
cmake-android-out/
cmake-out-android/
I can change build_x86_64 to cmake-out and build_android to cmake-android-out. It seems more consistent with other backends.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That sounds good
| -DPYTHON_EXECUTABLE=python3 \ | ||
| -DEXECUTORCH_SEPARATE_FLATCC_HOST_PROJECT=OFF | ||
|
|
||
| cmake --build $PWD -t "PyQnnManagerAdaptor" "PyQnnWrapperAdaptor" -j8 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any specific reason we use -j8 here and -j16 in the following cmake command?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No. I will fix this to avoid confusion.
Thank you for the promot review! |
|
Turning to draft. I will open the PR again after
|
|
Hi @cccclai , |
|
@cccclai has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
|
I ran into issues with the updated guide: |
|
Looks like cause by #4588 |