https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116809
--- Comment #1 from Iain Sandoe <iains at gcc dot gnu.org> --- yeah.. the compiler will not (for some several revisions) actually refer to libgcc_s.1.dylib - it is only there to support existing built exes from older compilers. Probably dropping it after macOS 14 is the best option - I'll look at amending the libgcc config to fix this. I don't have a macOS 15 install yet - running out of suitable hardware that is not already busy ....
