[BACKEND] Add iluvatar compute spec key specialization#708
Open
stringl1l1l1l wants to merge 1 commit into
Open
[BACKEND] Add iluvatar compute spec key specialization#708stringl1l1l1l wants to merge 1 commit into
stringl1l1l1l wants to merge 1 commit into
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
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
This PR moves iluvatar
compute_spec_keyspecialization behind the FlagTree backend spec mechanism, keeping the default Triton JIT path unchanged while enabling iluvatar-specific 4-byte divisibility keying.What’s included
spec_func("compute_spec_key")lookup in JIT binder creationcompute_spec_keyimplementation using 4-byte divisibilitythird_party/iluvatar/backend/spec/__init__.pyNotes
third_party/iluvatar/backend/spec/....