Emacs and GFortran

[David Kastrup]

Chong Yidong <cyd@stupidchicken.com> writes:

>> With the "simple" patch
>>
>>                 === gfortran Summary ===
>>
>> # of expected passes            12734
>> # of unexpected failures        2171
>> # of expected failures          7
>> # of unsupported tests          73
>
> If your test suites rely on a non-standard error-reporting format,
> bringing the format into standards-compliance will obviously break
> the test suites; but the bug here doesn't lie in the
> standards-compliance.

Certainly.  But it still means that changes in the format imply more
work in their wake than the original change warrants.  It also means
that one should be certain that one does all changes in one swoop so
that this followup work needs to be done only once.  So that means
that one needs to carefully round up _all_ cases and make sure one
does not overlook some.

This requires work, and it requires coordination in order to make sure
that the test suite does not go out of commission at a point of time
where it would be definitely needed desperately.  It might even be
prudent to make a branch for this purpose, and merge it only once when
it is completed.

So I do think the way to go is the one started: first enter this into
the bug database and take the discussion there, and then see when the
work could be done without causing too much disruption, and who would
be willing to work on it.

Fingerpointing is not going to help.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum