On Tue, Oct 31, 2017 at 09:30:27PM +0100, Thomas Koenig wrote: > > Or maybe emit diagnostics into the frontend optimize dump file and scan > > that? > > If we could check the Fortran tree dumps with dejagnu, that would be > doable. Unfortunately, we don't have that in place.
Well that should be rather easy. Don't we have a basic scan-dump where we can pass the file as well as a regexp? I might look into this later. > > This would be the difference between > > DO CONCURRENT test_do_speed:k 1:512:1,test_do_speed:j > 1:512:1,test_do_speed:i 1:512:1() > > and > > DO CONCURRENT test_do_speed:i 1:512:1,test_do_speed:j > 1:512:1,test_do_speed:k 1:512:1() > > Just about the only way I can think of is to add a warning > option if something is actually interchanged. Might be worth > doing anyway, but I would like not to add too many -W options. > > -fopt-info would be nice to have here (PR 66576). I had a > preliminary look at what it does for gcc, but after a look > at the source, I decided that this was not really self-explanatory > and that I'd rather do other things :-) ah right that would be a good idea, too. Thanks for the explanation! cheers,