https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116948
--- Comment #5 from Filip Kastl <pheeck at gcc dot gnu.org> --- We run the ubsan bootstrap roughly every week. We also have a simple script that searches the logs for errors. It looks like this find gcc/testsuite -name "*.log" | xargs cat | ... here we pipe output through some grep -v commands to eliminate these: fortran/simplify.c: poly-int.h: Fortran runtime error slice bounds out of range runtime error.*with length index out of range invalid memory address or nil pointer dereference (I'm not sure about the reasoning for all of these -- Martin Liška built this infrastructure) and then we grep -A10 -B10 for 'runtime error:'. This script finds an error about once in a few weeks, sometimes months, I think. Output of the script is good enough for a human. However, CI was mentioned. So I suppose we want something that is machine readable. But maybe this can be at least a starting point for some parsing tool.
