https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83252
--- Comment #9 from Dmitry Babokin <babokin at gmail dot com> ---
(In reply to Richard Biener from comment #8)
> I suppose one could try scripting something with -fdisable-{tree,rtl}-$dump
> and seeding the list of passes to enable/disable with -fdump-{tree,rtl}-all.
>
> Of course some -fdisable-* are "invalid" and will cause "interesting"
> downstream
> effects...
>
> Sometimes I do this manually for cases where it isn't obvious who's doing sth
> wrong...
The main downside of this approach is that it requires understanding of GCC
compiler internals. And GCC bug tracker doesn't even have generic "new bugs"
component to assign, which means people need to have secret knowledge about
compiler internals. Would be good to address this problem in the long run and
make bug filing process more friendly for outsiders.
Don't take me wrong, my bugs are almost always are addressed blazingly fast and
I'm super happy about it. But I still think there are things which can make
life for bug filing people easier.
