https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109054
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- As I tried to explain, because libgcc_s and libstdc++ are different libraries, there is nothing that can be done on the GCC side. You can avoid libunwind (which is a good idea, it is a terrible library from my past experience with it), or if you can't, make sure libgcc comes earlier in the search path, or that libunwind defines all the unwinder symbols (_Unwind_*) and not just a subset (so whole app uses one unwinder or another depending on search path, but not a mix of them).
