Hello, I just found the discussion on the devtoolset on SO: https://stackoverflow.com/questions/15599714/risks-of-different-gcc-versions...
confirming my guesses. You can use any new C++11/C++14 feature and your program will link dynamically to stock libstdc++. Any feature that is not present there will be linked statically with nonshared_libstdc++.a. The only cost would be additional binary size. I checked using few features and binary growth was ignorable. But definitelly one have to take it into account. The only problem I have for now is to bring all of machines I maintain to a stable 6.6 version. Which is >1000 machines :) The cos is well worth it :)
Regards, -Jarek
2016-05-20 21:16 GMT+02:00 Warren Young wyml@etr-usa.com:
On May 20, 2016, at 8:17 AM, Jarosław Bober jaroslaw.bober@gmail.com wrote:
ldd gives me: ldd a.out linux-vdso.so.1 => (0x00007fff6e5ff000) libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00000039d8400000)
In that case, I don’t see how you can be making use of any C++11/14 features that aren’t implemented by the compiler itself (e.g. type inference via “auto”) or purely in template form. Any feature that uses the compiled Standard C++ Library can’t be using the new library.
That may be useful for your purposes. _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos