Document what I was told on #gcc --- gcc/doc/install.texi | 8 ++++++++ 1 file changed, 8 insertions(+)
diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi index 643f3bb311f..12a6db1666a 100644 --- a/gcc/doc/install.texi +++ b/gcc/doc/install.texi @@ -3039,6 +3039,14 @@ current time the testing harness does not allow fine grained control over whether or not a test is expected to fail. This problem should be fixed in future releases. +At present (Jan 2020) you can expect routine failures in quality tests +related to the optimizer even on first-tier platforms such as x86_64. +Until the test suite behavior is improved, an effective way to proceed +is to run contrib/test_summary immediately after first build on a +clean tree, save the output, and treat that as a correctness baseline. + +After making your changes, run contrib/test_summary again and look for +regressions - that is, FAIL results where it was previously PASS. @section Submitting test results -- 2.20.1
