topic Implemented in 15.0. in Intel® Fortran Compiler

CONTIGUOUS attribute

styc — Sat, 02 Mar 2013 04:43:23 GMT

ifort compiles the attached program without complaining. I wonder if some kind of a diagnostic message is necessary for subroutine f, which invokes subroutine g with an argument that may or may not be contiguous.

current ifort:

TimP — Sat, 02 Mar 2013 11:30:34 GMT

current ifort:

test.f90(6): error #8375: Array section is not contiguous if it has stride other
than unity.
    call g(x(1 : 10 : 2)) ! no good
-------------^
test.f90(6): error #8372: If dummy argument is declared CONTIGUOUS, actual argum
ent must be contiguous as well.
    call g(x(1 : 10 : 2)) ! no good
-----------^
compilation aborted for test.f90 (code 1)

Quote:TimP (Intel) wrote:

styc — Sat, 02 Mar 2013 11:36:07 GMT

TimP (Intel) wrote:

current ifort:

test.f90(6): error #8375: Array section is not contiguous if it has stride other
than unity.
    call g(x(1 : 10 : 2)) ! no good
-------------^
test.f90(6): error #8372: If dummy argument is declared CONTIGUOUS, actual argum
ent must be contiguous as well.
    call g(x(1 : 10 : 2)) ! no good
-----------^
compilation aborted for test.f90 (code 1)

Line 6 is commented out. Please do not bring it back.

f receives a contiguous copy

TimP — Sat, 02 Mar 2013 14:27:55 GMT

f receives a contiguous copy and passes it on to g.

Quote:TimP (Intel) wrote:

styc — Sat, 02 Mar 2013 17:39:36 GMT

TimP (Intel) wrote:

f receives a contiguous copy and passes it on to g.

Seemingly that is not the case with ifort. If you fill with the original x with 1, 2, ..., 10 and print out x(1) and x(2) in g, you get 1 and 2. gfortran 4.7 packs the noncontiguous argument in f before passing it to g and prints out 1 and 3.

styc,

jimdempseyatthecove — Mon, 04 Mar 2013 13:14:32 GMT

styc,

IVF requires caller to pass CONTIGUOUS array when dummy argument attributed with CONTIGUOUS.
gfortran apparently creates temporary array (when caller's arg not contiguous). This is equivalent to the called subroutine having no interface (explicit or implicit) with regard to the array dummy attributed CONTIGUOUS. Analogous to F90 calling F77 subroutine with no interface.

Sounds like an interpritation of the standards issue. Steve may be able to comment on this.

Jim Dempsey

The Fortran standard changed

Steven_L_Intel1 — Mon, 04 Mar 2013 16:02:15 GMT

The Fortran standard changed in this area since Fortran 2008 was published. Intel Fortran follows the original text that says:

The CONTIGUOUS attribute specifies that an assumed-shape array can only be associated with a contiguous effective argument.

Interpretation F08/0061 changed this to:

The CONTIGUOUS attribute specifies that an assumed-shape array is contiguous.

This interpretation was part of the just-approved Corrigendum 2 - we haven't caught up to that yet, but we will. I have filed issue DPD200241665 regarding this change.

Quote:Steve Lionel (Intel)

styc — Mon, 04 Mar 2013 16:23:17 GMT

Steve Lionel (Intel) wrote:

The Fortran standard changed in this area since Fortran 2008 was published. Intel Fortran follows the original text that says:

The CONTIGUOUS attribute specifies that an assumed-shape array can only be associated with a contiguous effective argument.

Interpretation F08/0061 changed this to:

The CONTIGUOUS attribute specifies that an assumed-shape array is contiguous.

This interpretation was part of the just-approved Corrigendum 2 - we haven't caught up to that yet, but we will. I have filed issue DPD200241665 regarding this change.

Thanks for the clarification. In that case, is implied pack/unpack (à la gfortran) the expected behavior?

I would say that, yes, that

Steven_L_Intel1 — Mon, 04 Mar 2013 17:08:43 GMT

I would say that, yes, that is the expected behavior.

Implemented in 15.0.

Steven_L_Intel1 — Thu, 04 Sep 2014 17:57:07 GMT

Implemented in 15.0.