Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29529 Discussions

Nested associate statements internal compiler error

ivanp
New Contributor I
1,070 Views

Nesting associate statements leads to ICE's in both ifort and ifx. Here is a MWE which aborts:

associate(d => sin(42.0))
    associate(g => d)
        print *, g, loc(g) == loc(d)
    end associate
end associate
end

 Output of other compilers can be found in Compiler Explorer: https://godbolt.org/z/TE7z37vne

Labels (1)
0 Kudos
1 Solution
Igor_V_Intel
Moderator
570 Views

It was a bug in ifx 2025.2 and earlier. Fixed in 2025.3.

View solution in original post

5 Replies
ivanp
New Contributor I
578 Views

It looks like this has been resolved with version 2025.3.0.


0 Kudos
Igor_V_Intel
Moderator
571 Views

It was a bug in ifx 2025.2 and earlier. Fixed in 2025.3.

JFH
New Contributor I
559 Views

With my version of ifx the ICE has gone away but the output still looks wrong because the result of loc(g) == loc(d) is F. Gfortran gives T.

```

(lf) john:~$ ifx --version
ifx (IFX) 2025.3.0 20251010
Copyright (C) 1985-2025 Intel Corporation. All rights reserved.

(lf) john:~$ ifx associate.f90 && ./a.out
-0.9165215 F
(lf) john:~$ gfortran associate.f90 && ./a.out
-0.916521549 T
(lf) john:~$

```

0 Kudos
ivanp
New Contributor I
546 Views

We'd have to read the standard "fine-print" here. I'm not sure the results of `loc` extension are relevant here. I used it to determine if compilers are creating copies or not. Note that you cannot use `c_loc` on `g` or `d`, because they don't have the pointer or target attribute. 

0 Kudos
JFH
New Contributor I
529 Views

There is no standard "fine print" because the F2023 standard has no LOC intrinsic, and so gfortran and ifx must have provided it as extensions. The different outputs suggest that ASSOCIATE  was implemented in different ways that both work.

0 Kudos
Reply