https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80781
--- Comment #3 from René J.V. Bertin <rjvbertin at gmail dot com> --- Dumb because? I don't think I'd use the term even if the official GCC standpoint were that clang is the superior compiler anyway. The simple reality on the Mac platform is that you cannot have libstdc++ and libc++ in the same process if there's the slightest risk they'll be used on the same objects. You can either make the most of that situation, or not. In the latter case you could just as well drop the whole g++ build (= allow the other compilers to build without wasting time building a crippled compiler). I agree that a proper implementation would include a compiler argument like clang does. But like clang the default on Mac should be libc++ because it makes little to no sense to use another runtime. Also, I'm not really in a situation where I can drive the full implementation myself. I understood that feature requests are appropriate here and provided my patch more as a proof of concept than as a reference implementation.
