feat: support selector-local mixed quantization settings - #7
Open
rdzhu225 wants to merge 1 commit into
Open
Conversation
ceci3
approved these changes
Aug 28, 2026
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
--selectclausesactivation-bits,strategy,group-size,scale-dtype, andchunk-sizevocabulary per selectorint4/int8) so futurefp4/fp8formats remain unambiguouspack-quantized/int-quantizedformats and the officialmixed-precisiontop-level format when requiredInterface
The existing homogeneous interface remains unchanged:
Selector-local and homogeneous selectors cannot be mixed in one command. In selector-local mode,
activation-bitsandstrategyare required, so W8A16 groupwise, W8A16 per-channel, and W8A8 per-channel are distinguishable.Scope
Selector-local mixed quantization currently uses the checkpoint-only MSE path. GPTQ, AWQ, and AutoRound are rejected explicitly in this mode. Runtime-specific DeepGEMM integration is intentionally outside this change.
Validation
ruff check .136 passed, 1 skippedflagos_quant_infer/flagos:137 passedwo_aweights stored as INT8