GFortran MatterMost new Hosting

Hello all, As of today the free hosting of our MatterMost workspace is ended. The MatterMost cloud service organization decided to end free accounts. Fortunately, the platform is Open Source and we owe a tremendous gratitude to the Oregon State University Open Software Lab (OSUOSL)for providi

Possible funding of gfortran work

Hi all, I found this message in my spam folder tonight. Please look. I also sent a note to Damian on this. Maybe we can get someone to push forward on te native coarrays work? Other thoughts? Jerry

[PATCHES, Committed] As obvious

Committed as obvious: commit 061b13ed014ba0b6891800a5c7f852bf58e4d856 Author: Jerry DeLisle Date: Thu Feb 16 18:13:56 2023 -0800 Fortran Tests: Allow passing on mingw. gcc/testsuite/ChangeLog: * gfortran.dg/bind_c_array_params_2.f90: Add *-*-ming* to dg-final. and co

[patch, fortran] PR103506 [10/11/12/13 Regression] ICE in gfc_free_namespace, at fortran/symbol.c

Attached patch fixes this problem by allowing the namespace pointer to be set correctly regardless of error condition. Regression tested on x86_64_linux_gnu. OK for trunk and backports? Regards, Jerry Author: Jerry DeLisle Date: Sat Jan 28 20:00:34 2023 -0800 ICE in gfc_free_namespace

[patch, gfortran.dg] Allow test to pass on mingw

Hi all, Similar to a patch I committed a while ago for Cygwin, the attached patch allows it to pass on the mingw version of gfortran. It is trivial. Ok for trunk? Regards, Jerrydiff --git a/gcc/testsuite/gfortran.dg/bind_c_array_params_2.f90 b/gcc/testsuite/gfortran.dg/bind_c_array_params_2.f9

Error on left hand function reference

Hi all, I spotted this today on the Fortran-Lang Discourse. It would not be setting precednce for us to allow an extension and turn this into a warning with -std=gnu and an error of strict compliance is wanted. https://fortran-lang.discourse.group/t/error-the-leftmost-part-ref-in-a-data-ref-cann

[patch, fortran] ICE in attr_decl1, at fortran/decl.c:8691

The attached patch was provided by Steve Kargl. After exploring for possible other checks I settled on leaving the patch intact. Two existing test cases updated as different but sensible error messages resulted. Regression tested on main line. OK to commit? Regards, Jerry Author: Steve Kargl