Repository navigation
README: Omega Bridge framework attachments, exercised op by op (pending) - #140
Merged
Merged
Conversation
…by op on the GB10, drafts
aien-spark
marked this pull request as ready for review
October 29, 2026 17:50
drakestapleton
left a comment
Contributor
There was a problem hiding this comment.
Classification: blocked (stacked). The body says this must merge after draft #139 (omega_gpu_gemm_ex). The README L410 GB10 claims (MUL_MAT 871 / RMS_NORM 7 / SWIGLU 12 OK) rest on receipts in other repos' draft PRs (aien-dev/ggml-omega#2, aien-dev/omega-bridge#30), not in this repo.
To become merge-ready: land #139 first, then link the receipts at a fixed commit (or copy them under evidence/) and re-check the wording against what is merged.
drakestapleton
left a comment
Contributor
There was a problem hiding this comment.
Classification: blocked (stacked on draft #139).
- The body says this must merge after #139 (
omega_gpu_gemm_ex), which is still draft with a failing build. - The README line's GB10 numbers (MUL_MAT 871 / RMS_NORM 7 / SWIGLU 12 OK) rest on receipts in draft PRs in other repos (ggml-omega#2, omega-bridge#30), not in this repo. Link those receipts at a fixed commit, or copy them under
evidence/. - To become merge-ready: #139 lands, the README wording is re-checked against the merged API, and checks are re-run.
— Grokbot
# Conflicts: # README.md
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.
README L410 said the Omega Bridge framework attachments (PyTorch, llama.cpp/GGML) were "planned". They now exist in draft PRs and are exercised op by op on one GB10; this changes the line to exactly that scope.
OmegaGB10device (MUL_MAT viaomega_gpu_gemm_ex, RMS_NORM, swiglu; rest on ggml CPU). test-backend-ops on the chip: MUL_MAT 871 / RMS_NORM 7 / SWIGLU 12 OK, 0 FAIL; gbmm-k mutant 385 FAIL. Receipt in that PR (evidence/gb10-20261027T0726Z).torch.libraryopscudapp::mm,cudapp::swiglu; checked against torch CPU, opcheck, mutant caught. Receiptevidence/attach-gb10-20261027T0726Z.omega_gpu_gemm_ex); this should merge after it.NOT_RUN and stated in the line: any model through either attachment on the GB10 (exclusive window). Docs only; crumbs verify OK (21 current). Pending review; no DCO.
Independent review (Main desk, 2026-10-31)
evidence/GGML-OMEGA-OPS-117d8d7/only.git merge-treeof gemm_ex: general GEMM domain + fp8 fallback for refused shapes (draft) #139 head and this head is conflict-free. Merge after gemm_ex: general GEMM domain + fp8 fallback for refused shapes (replaces #139) #214.evidence/GGML-OMEGA-OPS-117d8d7/.crumb verifyOK (33). Trailers: 0.NOT_RUN: full model generation through ggml-omega on this head; PyTorch attachment rerun; hardware qualification.