https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96780
Bug ID: 96780
Summary: debuginfo for std::move and std::forward isn't useful
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
Target Milestone: ---
When debugging I don't want to step into std::move and std::forward, ever.
They're effectively just casts, and although g++ correctly optimises them away
to nothing, it leaves debuginfo that makes gdb step into them.
Is there any good reason to ever step into them, or could we special case them
in g++ to not emit any debuginfo, at least when inlined?
I tried adding __attribute__((__always_inline__,__artificial__)) but that
seemed to make it even worse.
