https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117834
--- Comment #8 from Gleb Mazovetskiy <glex.spb at gmail dot com> --- > If you want to make progress, and help keep it alive, then the best way is to > test regularly - in this case you need to bisect to find what change caused > the problem - and hopefully that will suggest a patch. I'm doing this in the context of making the latest GCC the default compiler in macports (https://github.com/macports/macports-ports/pull/26655), so once that is merged and the Tiger PPC buildbot is back, this will be built with every release. This and https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117857 are the only 2 things that I had to patch around to get gcc14 building on Tiger. It's actually a lot easier to build gcc14 for Tiger than an older gcc version, no doubt thanks to Iain's work.