Comparing changes

…e of their ops The compiled JVM leg executes ComputeGraphExecutor(graph, ctx.ops), so it already runs under whatever schedule the ops were built with; the graph/tape context just could not say so. New ScheduledOps seam (lang-core): scheduled ops report their Schedule and rebuild themselves for another one. DefaultCpuOpsBase/DefaultCpuOps/DefaultCpuOpsJvm/AccelerateCpuOps implement it; DefaultGraphExecutionContext answers `schedule` from its baseOps and `withSchedule` yields a sibling over rescheduled ops (visible downgrade for ops that know no schedule, as before). Tests: ComputeGraphExecutorScheduleTest (sdpa node routes its (batch, head) units through a probing schedule, bit-identical to sequential), DefaultGraphExecutionContextScheduleTest. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

The TensorOps contract already declared key/value as [batch, nKVHeads, …]; the CPU kernel required equal head counts and made callers tile K/V to the query head count. It now reads K/V through the head-group index (h / (nHeads / nKVHeads)), same loop order and arithmetic, so nKV == nHeads stays bit-identical and grouped equals tiled bit for bit (SdpaGqaParityTest, under a reversing schedule too). SKEEP-005 phase 2: this is the structural statement the compile lane lowers without materialising the expansion. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

…ing dim SKEEP-005 phase 2, "structure at compile time": when K/V carry fewer heads than Q, the converter reshapes Q to [b, nKV, nRep, Sq, hd] and both dot_generals batch over [b, nKV] with nRep a free axis. K/V are never broadcast or concatenated; the group structure is what the compiler backend tiles over, and no core count appears in the module. Explicit rank-4 masks keep their batch axis ([0, 1, 3, 4]); the dynamic key-length path is unchanged; non-dividing head counts are a conversion failure. Equal head counts emit byte-identical MLIR (existing tests). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

…advisory SKEEP-005 phase 2, the responsibility split: ScheduleAnnotationPass now applies structuralDefaults() (attention → parallel_dims [batch, heads]) to every op without a hint of its own, so an exported attention always states its structure; defaults may never carry a core count (init check). A parallelism arriving explicitly from the DSL is stamped and emitted unchanged but flagged advisory in a diagnostic — no compile-time consumer reads it, the compiled target chooses its worker count when the device is created. HloGenerator.corePasses(target) exposes the layout + schedule passes for exporters that trace their own tape. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

…ne, dumps SKEEP-005 gains "Key decision: who schedules what" (structure at compile time, cores at run time; mermaid + ownership table), the phase-2 compile lane, rollout/acceptance items and the answered open question; the "Algorithm and schedule" explanation gets the same decision; CHANGELOG. API dumps refreshed. Two lines change rather than add: DefaultCpuOpsBase now also implements ScheduledOps, and its `schedule` widened from protected to public — both widenings, no caller breaks. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

Navigation Menu

Uh oh!

Comparing changes

Open a pull request

Uh oh!

Commits on Sep 4, 2026

This comparison is taking too long to generate.

Uh oh!