https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93291
--- Comment #5 from David Malcolm <dmalcolm at gcc dot gnu.org> --- (In reply to seurer from comment #4) > Not sure if the patch was done but the failure changed a bit over the > weekend. > > New failures (update from 3684bbb022cd75da55e1457673f269980aa12cdf to > f4d83eba60b5b1292a7cae660f03a2377e92a845): > FAIL: gcc.dg/analyzer/pattern-test-2.c <unknown> == 0 (test for warnings, > line 21) > FAIL: gcc.dg/analyzer/pattern-test-2.c <unknown> != 0 (test for warnings, > line 21) > > New passes: > FAIL: gcc.dg/analyzer/pattern-test-2.c (test for warnings, line 21) > FAIL: gcc.dg/analyzer/pattern-test-2.c (test for warnings, line 21) I haven't applied the patch from comment #3 yet; I think what you're seeing is the effect of 8863f61c9c9dcec6003c4d61665b226569c0c3b2, which added unique names to the four dg-warning tests at line 21.
