[Bug libstdc++/104719] Use of `std::move` in libstdc++ leads to worsened debug performance
vittorio.romeo at outlook dot com
gcc-bugzilla@gcc.gnu.org
Mon Feb 28 17:20:45 GMT 2022
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104719
--- Comment #6 from Vittorio Romeo <vittorio.romeo at outlook dot com> ---
> The request is to replace it with some kind of magic that does the same as std::move without actually writing std::move.
More generally speaking, ensure that function such as `std::move`,
`std::forward`, `std::vector<T>::operator[]`,
`std::vector<T>::iterator::operator*`, and so on never appear in debugging call
stacks and do not affect performance in `-Og` (or even `-O0`.
I think the title for my issue is a bit too specific, but I'd like to make this
a wider discussion in how to mitigate debug performance overhead caused by C++
standard library abstractions.
More information about the Gcc-bugs
mailing list