On Tue, Oct 31, 2017 at 02:24:39PM +0100, Thomas Koenig wrote: > Hello world, > > here is a version of the patch for index interchange for FORALL > and DO CONCURRENT that I would like to commit. > > It introduces a new option for selecting (or deselecting) > the option, -ffrontend-loop-interchange. The reason for > this is simple: It is always possible that the heurisics in the > patch might make a bad choice, and the user should be able to > deselect this optimization when he has already optimized loop > ordering in his code. The new option is selected when > optimizing, the same way that -ffrontend-optimize is. > > No test case because I could not think of anything > that could test the nesting of loops. > > Regression-tested. OK for trunk?
s/shoud/should/; s/acessed/accessed/; s/indces/indices/; why are struct ind_type "n" and "num" int and not unsigned int? Can't you scan the original dump for something characteristic? Or maybe emit diagnostics into the frontend optimize dump file and scan that? thanks,
