Repository navigation
Make local compile backend configurable - #11
Closed
ryan-li-ryanllli-aws wants to merge 1 commit into
Closed
ryan-li-ryanllli-aws wants to merge 1 commit into
ryan-li-ryanllli-aws wants to merge 1 commit into
Conversation
Collaborator
Author
|
Superseded by #13, which retains the lazy helper reset/rebinding design and includes HF config initialization, typed torch.compile calls, compatibility defaults, and engine propagation coverage. |
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
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.
Summary
Why
TorchTitan-owned compile sites currently select the default backend before model configuration is available. A custom device backend therefore has to patch torch.compile process-wide, which also affects user and third-party compile calls. This change gives those sites one scoped backend setting while preserving current default behavior.
Test plan