http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44107
--- Comment #29 from Denis Excoffier <g...@denis-excoffier.org> --- (In reply to Iain Sandoe from comment #28) > Well, there is a fix - which is to update > /usr/lib/libgcc_s.dylib to a non-buggy version. I had understood that it was desirable not to replace libgcc_s.dylib. Personally, i use the sed command (shown in comment #17) to create my own libgcc_s.1.dylib, i install it with GCC in /usr/local (or equivalent) and try to always link with it (and usually succeed since i don't use any libraries that are already linked with /usr/lib/libgcc_s.dylib). For security matters, that's like replacing, however. In any case, that bug is not NEW any more.
