http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59948
--- Comment #4 from Jan Hubicka <hubicka at gcc dot gnu.org> --- About the inlining issue, am not really sure how to handle this without iterating optimizers and inliner like llvm does (Maxim had patch for this). I wonder if we can't just declare the operator () always_inline to make sure it is early inlined? It gets me to _M_empty call that we fail to inline because we do not inline into alwaysinlines (because of cycles) but then we do not iterate the early inliner anymore so we do not inline after inlining always inlines. This is quite broken :( Marking those two always inline should get things possible to be analyzed...
