https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70594
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Perhaps a way to reduce this (though not as a -fcompare-debug failure) would be to see if on the original testcase you get different code generation or different -fdump-final-insns= dump between normal GC parameters and additional --param ggc-min-expand=0 --param ggc-min-heapsize=0 Though it would be best to verify first if before the problematic commit you get the same code generation (and same -fdump-final-insns=).
