Describe the profile-guided build of game 1.1.1 and the session that trains and measures a profile.

The section described the build of the other game versions with an example for 1.4.3. It now says how make_game.py
takes a kit's profile and when it leaves it out, which LLVM releases write and read the file, which packages the
instrumented build and the merge need, and the steps of a training session for 1.1.1: the build command, where the
game is started, what to play, where the counts land, the merge, and the comparison of both builds with the runtime's
sampling profiler and its frame timings.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
chrg6
2026-11-12 22:29:11 -05:00
parent 0b974d04f1
commit b197136f56
3 changed files with 110 additions and 23 deletions

View File

@@ -1887,8 +1887,9 @@ int plat_stderr_path(char *out, size_t cap) {
// ---- process
#ifdef NX2NAVI_PGO_GEN
// compiler-rt's profile runtime (an instrumented build, tools/build_game.py --pgo gen). It writes its counters from an
// atexit handler, which _exit skips; __llvm_profile_dump writes them once and makes later writes no-ops.
// compiler-rt's profile runtime (an instrumented build: --pgo gen of tools/make_game.py or tools/build_game.py). It
// writes its counters from an atexit handler, which _exit skips; __llvm_profile_dump writes them once and makes later
// writes no-ops.
int __llvm_profile_dump(void);
#endif