https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88763
--- Comment #4 from David Malcolm <dmalcolm at gcc dot gnu.org> --- (In reply to Marius Messerschmidt from comment #3) > Sorry but I do not fully understand what you mean. Do you suggest using > different command line arguments? I believe Richard is referring to the internal API used for dumping; right now it's presumably just writing to a FILE *, and this doesn't show up for -fopt-info*. > So far I tried: > > -fdump-tree-all > -fdump-tree-unswitch > > and > > -fopt-info-all-optall > > But none of them told me the all the things that I would wish to know, most > important the reason why a particular loop was skipped during unswitching > (e.g. because it is not invariant or so (right now it already reports a few > things with -fdump-tree-unswitch like too-many-instructions or > too-many-branches)) Am taking a look.
