Re: [PATCH] Fortran: fix issue with impure elemental subroutine and interface [PR119656]

2025-04-09 Thread Harald Anlauf
Am 09.04.25 um 04:06 schrieb Jerry D: On 4/8/25 1:43 PM, Harald Anlauf wrote: Hi all, the attached patch fixes a rather strange 12/13/14/15 regression. When walking through the list of procedures in an interface to find the matching one, the code could remember an inferred type from a false mod

Re: Is ASSOCIATE implemented correctly in gfortran?

2025-04-09 Thread Mikael Morin
Hello, Le 08/04/2025 à 15:29, Andre Vehreschild a écrit : Hi all, while working at teams stuff I encountered some issue with the ASSOCIATE statement: 1. First of all: It does not open its namespace as it is expected to. I.e. the associate-name (referring to the term as used in F2018 11.1.3.1 R

Re: Is ASSOCIATE implemented correctly in gfortran?

2025-04-09 Thread Paul Richard Thomas
Hi Andre and Mikael, The associate block is added *after* the associate statement is matched and the associate_names added to the parent namespace; see parse.cc(parse_associate). nagfor and flang-new both behave in the same way as gfortran. So ifort and ifx are the odd ones out. In F2018 and F20

Re: Is ASSOCIATE implemented correctly in gfortran?

2025-04-09 Thread Andre Vehreschild
Hi Mikael, thanks for your input. Meanwhile I checked the compiler explorer https://godbolt.org/z/Ehbjefzab and got an in-decided picture of what could be the way to go. First of all, most of the compilers in compiler explorer are gfortran for different architectures. So I ignored them. I used t