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
