https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89530
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> --- (In reply to dcci from comment #5) > (In reply to Jakub Jelinek from comment #4) > > Also, we usually bisect which gcc revision introduced a problem and from > > that change we can often see what goes wrong quickly. Both Red Hat and SUSE > > have terrabytes of built gcc revisions to make such bisection faster. > > I see. Is this data available for the masses? No, it is behind VPNs etc. One can do a git-bisect or write his own script of course, the bisect seeds we have are just for those who do this several times a day and don't want to wait until stuff builds again and again.
