https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104180
--- Comment #7 from Alexandre Oliva <aoliva at gcc dot gnu.org> --- I've recommended before that, without any plan to implement consumers for this debug information, keeping it in place is mostly wasteful. AFAICT other debug stmts issued by front-ends could hit the same issue, but those are only theoretical IIRC. On the one hand, disabling the feature would hide the known problem that codegen is sensitive to such debug stmts, but on the other, we can cross that bridge if we get to it again.
