https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42159
--- Comment #30 from Pierre Ossman <ossman at cendio dot se> --- (In reply to Dominique d'Humieres from comment #29) > I can reopen the PR, but I don't see the point: > (1) I can reproduce the problem only on x86_64-apple-darwin10 with gcc > version 4.4.7 > (I get 'CAUGHT' for all the other revisions I have tested on > powerpc-apple-darwin9, x86_64-apple-darwin10, and x86_64-apple-darwin14. I'm not sure what we're doing differently in that case. Are you sure you are using libgcc_s from your gcc and not getting the routines from libSystem? What if you statically link libstdc++ and libgcc_eh like we do? > (2) You should be able to build 4.9 and 5.0 without any patch for > x86_64-apple-darwin* and a few for powerpc-apple-darwin9 and 5.0. Sorry, my bad. It was other issues preventing us from moving our development platform to 4.9. We should be able to do a test build. Do you think anything has changed since 4.8.4 though? > (3) Why are you not using a more recent version of OS X? We need to produce binaries that most people can run, and 10.6 seemed like a good cut-off for now. We did however see the same crashes running the binary on 10.10. We have not tested using a newer target for the gcc build though.
