https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100152
--- Comment #49 from lucier at math dot purdue.edu --- > > and "make; make -k check". > > Which, presumably, succeeded [repeatably?] (also presumably with some > failing tests, since we don't have a clean testsuite on macOS). It gave reasonable results, the summary is here https://gcc.gnu.org/pipermail/gcc-testresults/2021-May/691571.html > > I then applied the patch, configured, "make; make > > -k check" and the make check always stops with > > > > <stuff removed> > > Running > > /Users/lucier/programs/gcc/gcc-mainline/libstdc++-v3/testsuite/libstdc++-dg/ > > conformance.exp ... > > WARNING: program timed out. > > There's not quite enough information here - it would be useful to know which > test(s) timed out - running "make check -jN -k" (where N is some sensible > number for the cores on your machine) would help since that will then print > which tests timeout. I had previously tried "make -j20 -k check" and "make -j30 -k check", which both gave the same "WARNING: program timed out." message, but where, precisely, it timed out I couldn't tell. That's why I did it serially, let it run for a few days, and that's the last thing that printed, immediately after Running /Users/lucier/programs/gcc/gcc-mainline/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp ... > > > Sorry, I don't know what's going on. > > The proposed patch is experimental - I haven't had an opportunity to test it > across the range of platforms - it might be incomplete or incorrect.
