Updated XNNPACK delegate readme #45061
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added some info on XNNPACK delegate to avoid confusion cause by XNNPACK engine being single-threaded by default. Further details are available in the description of the following issue: tensorflow#42277
multiverse-tf
requested review from
multiverse-tf
and removed request for
talumbau
multiverse-tf
approved these changes
Dec 22, 2020
| @@ -63,6 +63,27 @@ bazel build -c opt --fat_apk_cpu=x86,x86_64,arm64-v8a,armeabi-v7a \ | |||
| //tensorflow/lite/java:tensorflow-lite | |||
| ``` | |||
|
|
|||
| Note that in this case `Interpreter::SetNumThreads` invocation does not take | |||
There was a problem hiding this comment.
Many thanks for catching this 👍
google-ml-butler
bot
added
kokoro:force-run
gbaned
added
ready to pull
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added some clarification on XNNPACK delegate to avoid confusion cause by XNNPACK engine being single-threaded by default.
Further details are available in the description of #42277 issue.