User XLA computations support. #2125
Merged
Conversation
This file contains hidden or 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
dlibenzi
force-pushed
the
xla_user_ops
branch
12 times, most recently
from
eeb15f5 to
6fc4573
Compare
JackCaoG
approved these changes
May 27, 2020
No, but the interesting bits are few 😉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Exposes XLA builder capabilities to the Python layer.
This allows faster development cycle when prototyping ops, and allow users to define pytorch operations in terms of raw HLO (via XLA builder APIs), without having to build new binaries.
There are still XLA builder ops missing, and documentation (API final shape under development).