mirror of
https://github.com/MobileGL-Dev/MobileGL
synced 2026-11-17 06:53:22 +09:00
[MG_Pipe, MG_Impl, MG_Backend, MG_Test] (Disaggregated): P5e c0e - the cross-package seams
- MGPipeBarriered(op, payload, applierState), IMPLEMENTED, not stubbed: the static wait-class column plus the two payload-derived escalations the contract names (an open XFB span, a draw carrying kDrawClientArrays). One function and two callers is the point - the emit table and the sink must reach the same answer or the client runs on while the server reads a value that has already moved. set_context_values now mirrors IsTransformFeedbackActive into the applier state as well, because a predicate that read it out of gPipeInputs would be reading the very block run-ahead stops filling. - MGPipeApplierCurrentRecordIsBarriered() with the writer beside it. It answers true by default and that IS the landed lockstep answer, not a stub: on a server without kCapRunAheadApply every record is barriered and CONTRACT-P5C's two exemption scopes keep working unchanged. - The sb applier fields (BoundShaderBuffers[3][84], the three windows, the writable masks and ShaderBuffersSerial) and the pg record fields (the three binding tails, Signature, BindingsSerial) with the two entry points MGPipeApplySetShaderBuffers / MGPipeApplySetProgramBindings declared and ABORTING BY NAME. - The by-handle backend seams in Managers.h with aborting bodies in one block: ResolveVaoTwin, ResolveTextureTwin, ResolveProgramTwin, SyncTextureToBackendByHandle, SyncMipmapsToBackendByHandle, and the FBO / RBO / program SyncToBackendByHandle overloads. Five packages sit on opposite sides of these calls - tx2 writes what fb calls, fb writes what tx2 needs, id rekeys the registries all three read - so the signature is fixed once here and each family replaces a body. Abort and not null: a resolver that answered null renders a blank draw and a sync that did nothing renders stale pixels, and both are green lanes. - Coverage.def's GetBufferBindingPoint -> SetShaderBuffers row with BOTH of its PipeFill.cpp switch arms and the pairing asserts, shape-only and inert. It lands with the contract package because PipeFill.cpp belongs to the contract package for the whole phase - an emitter enumerator whose dispatch arm lived in the family's worktree is the merge trap that file's own comment was written about. - FieldOwnership.def re-annotates the six object-class rows plus GetProgramForDispatch to "P5e (Espryt unbarriered), P7 (Magma)", and the strict-abort case follows the string, which IS the debt entry rather than decoration. kMGPipeMaxBufferBindingPoints is pinned against BufferState.h's 84 where both are visible. gen_pipe_field_ownership's refusal count is 8.
This commit is contained in:
@@ -2023,6 +2023,15 @@ namespace MobileGL::MG_Pipe {
|
||||
// emission gate is the subsystem bit plus the whole-record hash and nothing else.
|
||||
case MGPipeFieldEmitter::SetContextValues:
|
||||
return kMGPipeSubsystemResidualValues;
|
||||
// P5e's one emitted row (MG_Remote/CONTRACT-P5E.md §5.6): the indexed buffer
|
||||
// binding points. Written HERE at the contract commit, with the Coverage.def row
|
||||
// and EmittedCallSuppliesTheWholeField's arm beside it, for the reason
|
||||
// kMGPipeWiredSubsystems' block states one paragraph down - this file belongs to
|
||||
// the contract package for the whole phase, and an emitter enumerator whose
|
||||
// dispatch arm lived in the family's own worktree is the merge trap that block
|
||||
// exists to close. It is inert until that family's wired constant leaves 0.
|
||||
case MGPipeFieldEmitter::SetShaderBuffers:
|
||||
return kMGPipeSubsystemBufferBindings;
|
||||
case MGPipeFieldEmitter::kNone:
|
||||
break;
|
||||
}
|
||||
@@ -2091,6 +2100,15 @@ namespace MobileGL::MG_Pipe {
|
||||
MG_State::GLState::VertexArrayObject::MAX_VERTEX_ATTRIBS,
|
||||
"the MGPipe vertex-attribute capacity and the frontend's have drifted");
|
||||
|
||||
// P5e (MG_Remote/CONTRACT-P5E.md §1, ruling 10), pinned here for the same reason and in
|
||||
// the same place: this translation unit sees the frontend constant and the MG_Pipe one,
|
||||
// and nothing else does. 84 is what the emitter may describe and what the wire carries;
|
||||
// the BACKEND clamps to the device's real GL_MAX_UNIFORM_BUFFER_BINDINGS, as it does
|
||||
// today, because a client-side clamp would read a device capability from the wrong side.
|
||||
static_assert(kMGPipeMaxBufferBindingPoints ==
|
||||
MG_State::GLState::BufferBindingPointCount,
|
||||
"the MGPipe buffer-binding-point capacity and the frontend's have drifted");
|
||||
|
||||
// ---- P4a's SEVEN pairings, and EVERY ONE OF THEM COMPARES AGAINST
|
||||
// SubsystemForEmitter RATHER THAN AGAINST A CONSTANT. That is the lesson written out
|
||||
// twenty lines above and it is not a style preference: naming the subsystem constant
|
||||
@@ -2128,6 +2146,23 @@ namespace MobileGL::MG_Pipe {
|
||||
SubsystemForEmitter(MGPipeFieldEmitter::SetDispatchProgram),
|
||||
"set_draw_program and set_dispatch_program are one family and one A/B");
|
||||
|
||||
// P5e's pairing, in the same shape and for the same reason as P4a's seven: the two maps
|
||||
// answer different questions - one takes a field's EMITTER, the other a dirty BIT - and
|
||||
// the emission is gated on one while the residual-fill skip is gated on the other, so a
|
||||
// divergence would push a call whose field is still pulled, or skip a field whose call
|
||||
// was never emitted. Compared against SubsystemForEmitter rather than against the
|
||||
// constant, because pinning the two MAPS to each other is the statement that cannot
|
||||
// drift.
|
||||
static_assert(MGPipeSubsystemForDirty(MGPipeDirty::NewShaderBuffers) ==
|
||||
SubsystemForEmitter(MGPipeFieldEmitter::SetShaderBuffers),
|
||||
"set_shader_buffers and NEW_SHADER_BUFFERS must name one subsystem");
|
||||
static_assert(MGPipeSubsystemForDirty(MGPipeDirty::NewConstBuffers) ==
|
||||
MGPipeSubsystemForDirty(MGPipeDirty::NewShaderBuffers),
|
||||
"the three binding-point bits are one family and one A/B");
|
||||
static_assert(MGPipeSubsystemForDirty(MGPipeDirty::NewSoTargets) ==
|
||||
MGPipeSubsystemForDirty(MGPipeDirty::NewShaderBuffers),
|
||||
"the three binding-point bits are one family and one A/B");
|
||||
|
||||
// THE TEXTURE-RESOURCE SUBSYSTEM HAS NO DIRTY BIT, and that has to be asserted rather
|
||||
// than left as an absence: its calls are dispatched from the GL entry points that
|
||||
// cause them, so a bit that started naming it would gate the emission twice - once at
|
||||
@@ -2283,6 +2318,13 @@ namespace MobileGL::MG_Pipe {
|
||||
case MGPipeInputField::GetTextureUnitObject:
|
||||
case MGPipeInputField::GetProgramForDraw:
|
||||
case MGPipeInputField::GetProgramForDispatch:
|
||||
// P5e (CONTRACT-P5E.md §5.6): the same answer for the same reason. The field is
|
||||
// four raw bases into the frontend's binding-point table and set_shader_buffers
|
||||
// carries resolved {handle, offset, size} ranges; the applier cannot produce a
|
||||
// pointer, so skipping the pull would leave the mirror null on every draw of every
|
||||
// push build. What retires it is the four Espryt consumers reading the applier's
|
||||
// BoundShaderBuffers, not this row.
|
||||
case MGPipeInputField::GetBufferBindingPoint:
|
||||
return false;
|
||||
default:
|
||||
return true;
|
||||
|
||||
Reference in New Issue
Block a user