mirror of
https://github.com/ARMSX2/ARMSX2.git
synced 2026-08-24 16:50:16 -07:00
Brian Degenhardt
9a4bd0f56f
Both `gsctl stats` and `gsrunner -stats-json` reported counters with no indication of which GPU or driver produced them, so a stats blob from a tester was not attributable — and driver identity is the axis nearly every mobile GPU behaviour turns on. This matters beyond provenance. Several GS features are force-overridden per-driver (framebuffer fetch and texture barriers are forced on for Adreno regardless of INI), so without knowing the driver you cannot tell whether a settings A/B was applied at all or silently compared a config against itself. gsrunner captures the strings on the GS thread at first present rather than at shutdown, where the device may already be gone. Both emitters escape the values, since GetDriverInfo() is multi-line on Vulkan.