Just to tick a few points off the list:
- from my experience, gcc4.8, clang3.3 and VStudio2013 all have very solid C++11 support, and it is definitely production ready
- (meta-) build systems: cmake, premake, scons or similar meta-build-systems; these create Makefiles or IDE project files and generally simplify managing the build system for large multiplatform projects
- std::thread, std::atomic and std::chrono are really helpful for multi-platform development, since these areas hadn't been standardized before
- clang/llvm has a nice static analyzer, which is also integrated into the Xcode IDE on OSX (with a funky visualization of the "reasoning flow"), VStudio2013 also has a static analyzer built in
- I use UnitTest++ for unit testing, but I'm sure there are other choices,
UnitTest++ has a nice IDE integration both in Xcode and VStudio (basically, the test failure messages are formatted so that they can be parsed by the IDE, and you can simply click on them)
- you can even get C++11 support on somewhat exotic platform like emscripten, std::atomic and std::chronos work, std::thread not because of Javascript's limited threading model
- the new move-semantic is really useful for dynamic container classes, and generally handing complex objects around, and you get these improvements "for free" when using the standard containers
[edit: chronos -> chrono]