On Tue, Feb 7, 2017 at 5:19 AM, Richard Biener <rguent...@suse.de> wrote: > On Wed, 1 Feb 2017, Richard Biener wrote: > >> Applied as follows, bootstrapped & tested on x86_64-unknown-linux-gnu. > > And as shown by the new testcase (ICEing on the gcc-6-branch only) the > fix is not enough as breadth merging of loop and loop->next may pull in > other loops into the region. Eventually this also shows that only > trying to merge loop with loop->next may not find all valid scops > as loop and loop->next->next may eventually be successfully merged > (inner loops of a loop are not sorted in any particular way, SCoP > dection seems to assume dominance order).
Understood. I do not think we take this wrong assumption about loop order in other parts of Graphite. Thanks for the patch. Sebastian
