(In reply to comment #35) > I really think that implementing the full gcc abi-tag support is not > feasible for Clang. > So I would recommend to focus on compatibility with the single (new) ABI > alone.
Wait, are you suggesting we move *all* users of *all* operating systems for *all* users of Clang and LLVM to change to the new GCC ABI because it's easier for Linux distributions that happen to have prematurely chosen to move? This doesn't make sense... Even if we segregate this for Linux only, which wouldn't be pretty, we're still forcing *all* other Linux distributions that may want to have a Clang package to move to the new GCC ABI just because other distros have. Still doesn't make sense... FWIW, Clang and GCC are running very well on my Arch Linux with GCC 5.3.0 and GLIBCXX_3.4.21. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488254 Title: clang++ no longer ABI-compatible with g++ To manage notifications about this bug go to: https://bugs.launchpad.net/llvm/+bug/1488254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
