[Docs] (MG_Backend, MG_Backend/DirectGLES, MG_Impl/Pipe, MG_IntegrationTest/Scenarios, MG_State/GLState, MG_Test/Buffer, MG_Test/Util, MG_Util/Metrics): correct comments about retired switches and moved code

This commit is contained in:
2026-10-15 10:15:41 -04:00
parent 725a73e2b5
commit b1f36a71b5
11 changed files with 45 additions and 53 deletions
+2 -2
View File
@@ -777,8 +777,8 @@ namespace MobileGL::MG_Util::PipeStats {
// P6 gate 8's two per-frame numbers have their JSON homes where every other ByteClass and
// CallClass already does - the `bytes` and `calls` blocks above, under their long names
// (stage-segment-bytes, wire-records) - so there is nothing to add for them here. The
// staged-blob DISTRIBUTION does need one: it is the deliverable MEASUREMENTS.md §6.3 says
// has never been measured, and like the draw-payload histogram above it is a run-total
// staged-blob DISTRIBUTION does need one: it is the per-blob distribution after chunking,
// first measured through this dump, and like the draw-payload histogram above it is a run-total
// distribution, which is exactly what Tracy cannot plot and this dump exists to carry.
// Bucket 0 is "0 bytes" and bucket n>0 is [2^(n-1), 2^n): the same edges PayloadBucketOf
// gives both histograms, so the two are read the same way.
+2 -2
View File
@@ -421,9 +421,9 @@ namespace MobileGL::MG_Util::PipeStats {
// populations: the one above is the command payload of a draw (plan section 4.5.7, sizing
// SEG_CMD), this one is how big the blobs a workload stages into SEG_STAGE actually are.
//
// IT EXISTS FOR CONTRACT-P6.md §9 item 8, and MEASUREMENTS.md §6.3 says in as many words why:
// IT EXISTS FOR CONTRACT-P6.md §9 item 8, for this reason:
// the chunking work landed (1e7c372e buffer walks, 9469d48e texture slabs) and every
// `maxrec` number the file carries predates it, so "the per-blob byte distribution after
// `maxrec` number then on record predated it, so "the per-blob byte distribution after
// chunking" had no measurement at all. A per-frame AVERAGE cannot answer it either: an
// average of 8 MiB is the same number whether one blob of 8 MiB was staged or two of 4 MiB
// that the budget should have cut to one. The bucket edges are PayloadBucketOf's, shared so