https://gcc.gnu.org/bugzilla/show_bug.cgi?id=125485
--- Comment #8 from Drea Pinski <pinskia at gcc dot gnu.org> --- (In reply to Dennis Clarke from comment #5) > The testsuite fails to complete. It fails to run to completion. This > has nothing to do at all with separate components inside the testsuite > returning a FAIL. I have done this for decades and generally the entire > testsuite runs until I get a final timestamp and the final state in the > shell is a zero value status. As I mentioned that is not how GCC testsuite works. (maybe it should but currently does not). Also about slow running of the testsuite; if you have multiple cores you can use the -j option for `make -k check` to use all of the cores. Yes GCC testsuite is huge and non-parallelized runs can take more than 24 hours to run. Also running the GCC testsuite is not for the faint of heart. For all of the failures you see via contrib/test_summary, you have to go and analyze each one to see if it is a missed optimization or testing wrong code.
