From eb8298432e369a2b541f1ab467affa36581cf8ce Mon Sep 17 00:00:00 2001 From: Kim Morrison <477956+kim-em@users.noreply.github.com> Date: Fri, 28 Nov 2025 23:56:59 +1100 Subject: [PATCH] doc: clarify how to trigger automatic stage0 updates (#11413) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This PR clarifies the bootstrap documentation to explain that to trigger the automatic stage0 update mechanism, you should modify `stage0/src/stdlib_flags.h` (not `src/stdlib_flags.h`). The existing text was ambiguous about which file to modify. 🤖 Prepared with Claude Code Co-authored-by: Claude --- doc/dev/bootstrap.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/dev/bootstrap.md b/doc/dev/bootstrap.md index 8e889f4726..d055f73702 100644 --- a/doc/dev/bootstrap.md +++ b/doc/dev/bootstrap.md @@ -72,6 +72,9 @@ update the archived C source code of the stage 0 compiler in `stage0/src`. The github repository will automatically update stage0 on `master` once `src/stdlib_flags.h` and `stage0/src/stdlib_flags.h` are out of sync. +To trigger this, modify `stage0/src/stdlib_flags.h` (e.g., by adding or changing +a comment). When `update-stage0` runs, it will overwrite `stage0/src/stdlib_flags.h` +with the contents of `src/stdlib_flags.h`, bringing them back in sync. NOTE: A full rebuild of stage 1 will only be triggered when the *committed* contents of `stage0/` are changed. Thus if you change files in it manually instead of through `update-stage0-commit` (see below) or fetching updates from git, you either need to commit those changes first or run `make -C build/release clean-stdlib`.