https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81419
--- Comment #2 from Eric Gallager <egallager at gcc dot gnu.org> --- (In reply to Martin Sebor from comment #1) > Confirmed. There are few other similar bugs for these fix-it hints (e.g., > pr80567 or pr80684). I haven't looked at the implementation but from the > symptoms it feels like the problem is that the search doesn't fully consider > the context in which the undeclared is used. I.e., it doesn't distinguish > between a function call, other kinds of expressions, a type, or even a > keyword, etc. Hopefully GCC can learn to make these distinctions in time for GCC 9.
