Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

pytorch / xla Public

Notifications You must be signed in to change notification settings
Fork 487
Star 2.5k

Code
Issues 593
Pull requests 147
Actions
Projects 11
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

Automatically move CUDA non XLA Tensors to XLA Device and back to CUDA device#6644

Merged

changm merged 3 commits intomasterpytorch/xla:masterfrom changm/automovepytorch/xla:changm/automoveCopy head branch name to clipboard

Mar 13, 2024

+110-3

Conversation Commits3 (3)Checks Files changed

Commits

Commits on Mar 11, 2024

Automove CUDA tensors to xla device if they aren't already on the XLA device
changm
committed
Clear metrics for test and remove redunant call
changm
committed
Assert device exists when moving to a target device
changm
committed

Footer

© 2024 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.