This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [patch, fortran] Index interchange for FORALL and DO CONCURRENT
- From: Thomas Koenig <tkoenig at netcologne dot de>
- To: Bernhard Reutner-Fischer <rep dot dot dot nop at gmail dot com>
- Cc: "fortran at gcc dot gnu dot org" <fortran at gcc dot gnu dot org>, gcc-patches <gcc-patches at gcc dot gnu dot org>
- Date: Fri, 3 Nov 2017 22:08:18 +0100
- Subject: Re: [patch, fortran] Index interchange for FORALL and DO CONCURRENT
- Authentication-results: sourceware.org; auth=none
- References: <e3c94fe7-3e1e-8fce-5efe-fb966cfe93cb@netcologne.de> <20171031163621.ry2bqactzrzvftkg@nbbrfq.cc.univie.ac.at> <094b1136-3624-f0d3-9bf0-c7eea5a9ba6f@netcologne.de> <20171031205037.yhkyscamtszul5gi@nbbrfq.cc.univie.ac.at> <20171031205645.ltxgquz6nr45nqtq@nbbrfq.cc.univie.ac.at>
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 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.
and there is a scan-lang-dump which may be exactly for this case.
I have looked at this a little, and currently, there is no easy
way to scan the dump from -fdump-fortran-original.
My preference would be to commit the patch as is and open a PR
for scanning the dump, with a note about the missing test case.
So, is the original patch (with the spelling corrections) OK for trunk?
Regards
Thomas