https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93883
--- Comment #5 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- On Sat, 22 Feb 2020, roland.illig at gmx dot de wrote: > The diagnostics in the test should be as close to the diagnostics in the main > code, in order to make it easy to find them. I think it's a feature, not a bug, for tests to contain only a substring of the diagnostic that's sufficient to indicate it's a relevant diagnostic rather than something unrelated, as it reduces the likelihood of many tests needing updating for minor improvements to the wording of a diagnostic. To find examples of tests that trigger a diagnostic, I advise running the GCC testsuite then looking in the resulting .log files (gcc.log, g++.log, etc.). I did that in the past (comparing the results to diagnostics from gcc.pot) to identify untested C front-end diagnostics, and then added tests for them to the testsuite, although I haven't done such a check recently.
