https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111050
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to François Dumont from comment #1) > It seems to be a limited issue as you need a non-optimized build. That's not a safe assumption. Inlining decisions can change across builds and across architectures, and it's not safe to assume the affected functions will always be inlined, e.g. in the presence of explicit instantiation definitions. > The only > impacted member is the _M_next() which is a simple static_cast, I'm very > surprised that it's not always inlined even if non-optimized. No functions are inlined for non-optimized builds, unless forced with always_inline.
