3 ms·
What's the issue with abi stability? GCC broke the Library ABI with C++11 but the old ABI was still available. I thi k it still available in C++14 and 17 mode.
by gpderetta 7y ago
What's the issue with abi stability? GCC broke the Library ABI with C++11 but the old ABI was still available. I thi k it still available in C++14 and 17 mode.
If you switched to the new ABI with c++11 then c++17 as far as I know brings no new breakages.
- deleted 7y ago[deleted]
- CoolGuySteve 7y agoNo, std::string definitely changed between c++11 and c++14. It could be an implementation detail between different libstdc++ versions for the g++ version that supported c++14, but the incompatibility was definitely there.
- jcelerier 7y ago> No, std::string definitely changed between c++11 and c++14. It could be an implementation detail between different libstdc++ versions for the g++ version that supported c++14, but the incompatibility was definitely there. that is a problem with your distribution (and the reason why using distro packages sucks for development), not with C++. The ABI only changes if you change the value of _GLIBCXX_USE_CXX11_ABI with libstdc++ See : https://gcc.godbolt.org/z/QLbjjo https://gcc.godbolt.org/z/QLbjjo
- CoolGuySteve 7y agoYour example breaks if you change the C++11 pane to GCC 4.9 or earlier, which is the default in CentOS 7 and Ubuntu 14.04. Considering that was only 5 years ago, I wouldn't consider this a stable ABI.
- jcelerier 7y agobut again you can revert to gcc-4.9 behaviour with -D_GLIBCXX_USE_CXX11_ABI=0