mirror of
https://github.com/MobileGL-Dev/MobileGL
synced 2026-11-17 23:13:22 +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:
@@ -9,7 +9,7 @@
|
||||
"""Per-symbol nm/.text attribution between two libMobileGL.so builds.
|
||||
|
||||
P0.5's acceptance gate says every `nm --defined-only -S` delta has to be explainable per
|
||||
symbol (ROADMAP.md:16). The awkward part is that de-nesting a type renames every mangled
|
||||
symbol. The awkward part is that de-nesting a type renames every mangled
|
||||
name that mentions it - `ProgramObject::LinkArtifacts` -> `LinkArtifacts` shows up inside
|
||||
every `std::vector<...>` instantiation too - so a raw nm diff of a pure move looks
|
||||
catastrophic. `--strip-scope` folds those into a "renamed-only" bucket: same normalised
|
||||
@@ -30,8 +30,8 @@ GUARD RAILS - the comparison is meaningless unless both .so files were built wit
|
||||
The header of every report prints both paths and their byte sizes so a mismatched pair is
|
||||
visible in the output rather than only in the reader's assumptions.
|
||||
|
||||
This tool is informational by default (ARCHITECTURE.md:507, job name `monolith-symbol-report`
|
||||
ARCHITECTURE.md:568): with no gate flag it prints its report and exits 0, whatever it found.
|
||||
This tool is informational by default (ARCHITECTURE.md §13.2, job name `monolith-symbol-report`
|
||||
ARCHITECTURE.md §16): with no gate flag it prints its report and exits 0, whatever it found.
|
||||
Three flags turn it into a hard gate, and P1's G1 uses the first two - the strangler's pull build
|
||||
has to stay byte-identical, and G1 spells that out as `added == removed == resized == renamed == 0`
|
||||
with a `.text` delta of zero:
|
||||
|
||||
Reference in New Issue
Block a user