Re: [patch, fortran] Index interchange for FORALL and DO CONCURRENT

2017-11-03 Thread Thomas Koenig
Am 31.10.2017 um 21:56 schrieb Bernhard Reutner-Fischer: On Tue, Oct 31, 2017 at 09:50:37PM +0100, Bernhard Reutner-Fischer wrote: 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 th

Re: [patch, fortran] Index interchange for FORALL and DO CONCURRENT

2017-10-31 Thread Bernhard Reutner-Fischer
On Tue, Oct 31, 2017 at 09:50:37PM +0100, Bernhard Reutner-Fischer wrote: > 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, tha

Re: [patch, fortran] Index interchange for FORALL and DO CONCURRENT

2017-10-31 Thread Bernhard Reutner-Fischer
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

Re: [patch, fortran] Index interchange for FORALL and DO CONCURRENT

2017-10-31 Thread Thomas Koenig
Hi Bernhard, Regression-tested. OK for trunk? s/shoud/should/; s/acessed/accessed/; s/indces/indices/; Fixed. why are struct ind_type "n" and "num" int and not unsigned int? I tend not to use signed variables unless the special overflow semantics are required. I like Fortran, which does

Re: [patch, fortran] Index interchange for FORALL and DO CONCURRENT

2017-10-31 Thread Bernhard Reutner-Fischer
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-interchang