https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102511
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Aldy Hernandez from comment #6) > Describing the process to get here makes it abundantly clear that we need to > improve the process of debugging this. We need a way to turn on the solver > debugging from the command line (--param??), and not by some magic #define. > Also, some counter that matches the path being registered with the > equivalent solver dump would be useful. This way someone could easily find > the problematic thread in the solver dump. I'll look into this. Maybe look into dbgcnt.def and their usage. It should help with the counter situtation :).
