https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89530
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
In GCC people don't disable passes usually, but just use -fdump-tree-all and/or
-da and look at the dumps where it broke. We do have
-fdisable-<kind>-<pass>{,=range-list} options to disable individual passes if
needed, or various -fno-tree-* or -fno-rtl-* etc. options, but it can give
surprising result if you disable too many and just using binary search in the
pass dumps is much better (start looking at -fdump-tree-optimized dump if it is
a GIMPLE or RTL issue, depending on that look at some pass in the middle of the
either range, etc.
