https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116809
--- Comment #11 from Iain Sandoe <iains at gcc dot gnu.org> --- Indeed, all of this is well-known; NOTE: there is no change proposed for any OS < macOS 15. We actually bumped our libgcc_s version some time ago because GCC has for a while now been pulling the unwinder directly from libSystem (or /usr/lib/libgcc_s.1.dylib on darwin9). So GCC will not (for several releases now) be emitting any reference to libgcc_s.1.dylib - and on darwin9 (which actually needs the installed /usr/lib/libgcc_s.1.dylib) as said, there's no change proposed To use the GCC legacy lib - you'd have to use DYLD_LIBRARY_PATH to force point to an installation - otherwise the installed version in /usr/lib would (and should) be used anyway .. My view is that we want to remove this sometime - like Apple, eventually "legacy" has to be "we no longer care" .. so my preference is to remove it - and if we should get fallout - then we can consider an alternate solution with an edited symbols list.
