mirror of
https://github.com/MobileGL-Dev/MobileGL
synced 2026-11-20 00:11:56 +09:00
[Docs] (.github/workflows, CMakeLists.txt, MG_Backend, MG_Backend/DirectGLES, MG_Backend/DirectVulkan, MG_Backend/MGPipe, MG_Backend/Record, MG_Impl/Pipe, MG_IntegrationTest, MG_IntegrationTest/Harness, MG_IntegrationTest/Scenarios, MG_Pipe, MG_Remote, MG_Remote/Client, MG_Remote/Server, MG_Remote/Transport, MG_Remote/Wire, MG_State/GLState, MG_Test, MG_Test/Buffer, MG_Test/Purity, MG_Test/Util, MG_Test/Wire, MG_Util/Metrics, MobileGL, scripts, tools/trace_replay): replace stale line-number citations with sections and symbols
This commit is contained in:
@@ -777,7 +777,7 @@ 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:342 says
|
||||
// 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
|
||||
// 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
|
||||
|
||||
@@ -421,7 +421,7 @@ 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:342 says in as many words why:
|
||||
// IT EXISTS FOR CONTRACT-P6.md §9 item 8, and MEASUREMENTS.md §6.3 says in as many words why:
|
||||
// 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
|
||||
// chunking" had no measurement at all. A per-frame AVERAGE cannot answer it either: an
|
||||
|
||||
Reference in New Issue
Block a user