------- Comment #5 from rguenth at gcc dot gnu dot org 2006-10-16 16:06 ------- Doesn't work out. It looks like we depend on its side-effects in some testcases:
FAIL: gcc.dg/assign-warn-3.c (test for warnings, line 9) FAIL: gcc.dg/assign-warn-3.c (test for warnings, line 13) FAIL: gcc.dg/pr29254.c (test for warnings, line ) FAIL: gcc.dg/pr29254.c (test for warnings, line 21) FAIL: gcc.dg/warn-1.c (test for warnings, line 15) FAIL: gcc.dg/noncompile/pr16876.c (internal compiler error) FAIL: gcc.dg/noncompile/pr16876.c (test for errors, line 10) ... pr29254 is artificial - it tests for the bogus warning, otherwise the warning should be done in the frontend. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29478
