C++11 language support in g++ without the library-breaking features of `-std=c++11`

Question

Is there a way to tell g++ to enable the new language features of C++11 without any breaking changes to the standard C++ library due to ABI modifications?

Adding the -std=c++11 compilation flag tells g++ to enable both the language and the library features, but object files created this way cannot be safely linked with those that used a different -std= setting. I'd like to be able to use language enhancements like rvalue references, move constructors (for my own classes), and the auto keyword in code that's linked against C++03 libraries.

EDIT:

I'm interested in having g++ enable its C++11 language features, but I want it to parse, compile, and link against the old C++03 libraries. I don't want it to use the C++11 version of the standard library. This means that in my own code, I'll be able to use auto, range foreach constructs, rvalue references, etc., but I won't be able to use the new C++11 features in the standard C++ library like std::move or rvalue-ref enhancements to the STL containers. The reason for not wanting the C++11 version of the standard library is that the layout of various objects has changed, so it's invalid to link two object files that expect different versions of the standard library into the same binary.

Answer 1

No, you can't enable C++11 language features without C++11 library features (not without editing the libstdc++ headers to remove all the C++11 parts.)

But there aren't many incompatible symbols (as long as you don't use 4.7.0 or 4.7.1 which had an incompatible std::list, reverted for 4.7.2) so you probably only need to worry about the erase() members of the RB-tree containers. You could ensure the C++11 version of the symbol is defined in your main executable, so that version of the symbol will be used by all code that needs it. Code in other libraries expecting the C++03 versions will ignore the return value, code expecting the C++11 versions will be able to use the return value.