Re: Patch for fortran/62536 and fortran/66175

2015-08-24 Thread FX
> This patch cleans up nested blocks when there's an unexpected end of a > compilation unit (66175), and it handles cleaned-up blocks gracefully > (62536). I've run "make check-fortran" with the attached test cases. I have now committed the patch to trunk as revision 227135. Thanks for your con

Re: Patch for fortran/62536 and fortran/66175

2015-08-01 Thread FX
> No, I don't, but I would be happy to assign copyright. How do I do that? I've > read this: https://www.fsf.org/licensing/assigning.html > and it says I should "email the maintainer of the program communicating [my] > desire to assign copyright.” As I understand it, you need to fill this form:

Re: Patch for fortran/62536 and fortran/66175

2015-08-01 Thread FX
> This patch cleans up nested blocks when there's an unexpected end of a > compilation unit (66175), and it handles cleaned-up blocks gracefully > (62536). I've run "make check-fortran" with the attached test cases. The patch is OK. But the question I missed in my earlier email was: do you hav

Patch for fortran/62536 and fortran/66175

2015-07-31 Thread Louis Krupp
This patch cleans up nested blocks when there's an unexpected end of a compilation unit (66175), and it handles cleaned-up blocks gracefully (62536). I've run "make check-fortran" with the attached test cases. Index: ChangeLog ===