Hi Jorge, As I posted in the Intel Community, the error generated by gfortran (and nagfor) is consistent with the F2003 constraint: C1210 (R1209) The IMPORT statement is allowed only in an interface-body.
Could you please raise a problem report in gcc Bugzilla? Thanks Paul On Fri, 2 Jun 2023 at 15:04, Jorge D'Elia via Fortran <fortran@gcc.gnu.org> wrote: > > Hi, > > I have a doubt about IMPORT and SELECT TYPE, please see the > forwarded message below (that also has a sample code), as well > > https://www.ibm.com/docs/en/xffbg/121.141?topic=attributes-import-fortran-2003 > > What is the correct way? Thanks. > > Regards. > Jorge. > > ----- Forwarded message ----- > From: "Intel Community" > To: "Jorge D'Elia" <jde...@cimec.unl.edu.ar> > Sent: Viernes, 2 de Junio 2023 10:28:31 > Subject: Re: Bug with IMPORT and SELECT TYPE (Intel Community Subscription > Update) > > Hi jdelia, > > OP1 (New Contributor II) posted a new reply in Intel® Fortran Compiler on > 06-02-2023 10:28 AM in the Intel Community: > > https://community.intel.com/t5/Intel-Fortran-Compiler/Bug-with-IMPORT-and-SELECT-TYPE/m-p/1492319/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufExJRUxQQzhSUEVaS1RTfDE0OTIzMTl8U1VCU0NSSVBUSU9OU3xoSw#M166583 > > Subject: Re: Bug with IMPORT and SELECT TYPE > > Well, it appears that gfortran also gets it wrong... the use of an IMPORT > statement is not limited to interfaces. > See this paragraph from the Intel documentation: An IMPORT statement can > appear in a submodule, module procedure, > a contained procedure, the specification part of a BLOCK construct, or in an > interface body. It can not appear in > the specification part of a main program, external procedure, module, or > block data except in an interface body. > > -- -- "If you can't explain it simply, you don't understand it well enough" - Albert Einstein
