Re: v3 testsuite PATCH to avoid dg-excess-errors

2011-06-10 Thread Paolo Carlini
On 06/10/2011 10:36 AM, Jonathan Wakely wrote: I'll look at the broken tests asap, but that will be after work in about 8 hours. I'm ok if you want to go ahead and commit the patch, but if you do let's warn HJ that the regression testers will see the FAILs. Thanks Jon. The good news is that the

Re: v3 testsuite PATCH to avoid dg-excess-errors

2011-06-10 Thread Jonathan Wakely
On 10 June 2011 04:45, Jason Merrill wrote: > > Doing this revealed that the bind/ref_neg.cc test was broken; the dg-error > tags were missing a space before the closing }, so they were being ignored. >  When I fix that, I find that two of the tests are failing. Doh. > I'm committing the first pa

v3 testsuite PATCH to avoid dg-excess-errors

2011-06-09 Thread Jason Merrill
dg-excess-errors is a very large hammer that is rarely what you want to use. To filter out certain messages, it is better to use dg-prune-output. So this patch removes most of the dg-excess-errors from the v3 testsuite, replacing some with dg-prune-output, but most need no replacement. Doin