[ExecuTorch][WebGPU] Add Gemma 4 MTP export path - #21676
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/21676
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 New FailuresAs of commit c4dd7e2 with merge base ceca90f ( NEW FAILURES - The following jobs have failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This PR needs a
|
|
Hi @JCNTH! Thank you for your pull request. We require contributors to sign our Contributor License Agreement, and yours needs attention. You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
Stack from ghstack (oldest at bottom):
Export the official Gemma 4 target plus trained QAT assistant as a source-verifiable
k2_roundprogram. The model path preserves BSHD cache ownership, converts donor views to BHKD on the sequence dimension, advances assistant positions correctly, applies Gemma embedding scale, and rewrites only provenance-certified TopK/scatter sites. Publication is transactional and requires a hashed source receipt before combined staging.Key changes:
eagle_webgpu_round.pyimplements donor views, assistant steps, position progression, embedding scale, and residual provenance checks.Plain Gemma remains unchanged and independently landable.
Co-authored-with: Claude Code.
Differential Revision: D115234081