[PATCH] Temporarily enable ac_fold_checking for --enable-checking=yes.

[Eric Botcazou]

> I have two concerns.  First, I think some of the testing we do is not
> delivering value proportional to cost.  Is 20061226-1.c (sp?) really
> delivering anything close to the same percent of our quality that it
> costs in testing?  If not, should we let it take up several percent of
> our testing?

gcc.c-torture/compile/20001226-1.c to be precise.  FWIW, the first thing I do 
before testing on SPARC machines is 'rm gcc.c-torture/compile/20001226-1.c'.

> Maybe we could have one or two people running autotesters with lots and
> lots of checking turned on, and then reinforce the idea that a solemn
> responsibility of contributing GCC is fixing regressions that you
> introduce?

I think that we could be more clever in our testing strategy.  First, 
demanding tests should be set aside in a specialized testsuite not run
by default by 'make -k check' (e.g. the new gcc.c-torture/compile/limits-*).
People would be requested to run them only when maintainers explicitly ask.

Second, we could do the same for checking.  I think that there is little value 
in boostrapping with fold checking on when you're hacking the RTL middle-end, 
and vice-versa.  So we could settle on a moderate checking level by default 
and again maintainers would ask more on a case-by-case basis.

-- 
Eric Botcazou