All, Paul recently committed a change that brings gfortran's IMPORT statement into conformance with the Fortran 2018 and 2023. (Thanks, Paul!).
Here's a note for the Release Notes. I'm not who needs to approve this or who can actually do the commit. diff --git a/htdocs/gcc-16/changes.html b/htdocs/gcc-16/changes.html index cc6fe204..0348b90b 100644 --- a/htdocs/gcc-16/changes.html +++ b/htdocs/gcc-16/changes.html @@ -98,7 +98,18 @@ for general information.</p> <!-- <h3 id="d">D</h3> --> -<!-- <h3 id="fortran">Fortran</h3> --> +<h3 id="fortran">Fortran</h3> --> + +<ul> + <li> + The <code>IMPORT</code> statement has been brought into conformance + with the Fortran 2018 and 2023 standards. It can now appear in a + contained subprogram or <code>BLOCK</code> construct to restrict access + via host association. All numbered constraints within these Fortran + standards should report nonconforming uses of <code>IMPORT</code>. +</li> +</ul> + <!-- <h3 id="go">Go</h3> --> -- Steve
