BUG: Problems Passing Arguments to ENTRY Statement

• Microsoft FORTRAN for OS/2, versions 4.1, 5.0, and 5.1

SYMPTOMS

Programs compiled with Microsoft FORTRAN versions 4.0, 4.01, 4.1, 5.0, and 5.1 can generate a protection violation when run under OS/2, if a program contains the following:

1. An ENTRY statement to enter a SUBROUTINE or external FUNCTION

2. A CALL to the SUBROUTINE or external FUNCTION

3. An argument that is referenced in the ENTRY statement but not in the SUBROUTINE or external FUNCTION statement, and is then used in the ENTRY section of the SUBROUTINE or external FUNCTION.

RESOLUTION

To avoid this problem, pass the argument to the SUBROUTINE or external FUNCTION as well as to the ENTRY point.

STATUS

Microsoft has confirmed this to be a problem in FORTRAN versions 4.0, 4.01, 4.1, 5.0, and 5.1 for OS/2. We are researching this problem and will post new information here as it becomes available.

MORE INFORMATION

The following example illustrates the problem:

      i=0
      call sub
      end

      subroutine sub
      entry entersub(i)
      i=0
      i=i+1
      write(*,*) i
      end

      1

Passing the argument to the SUBROUTINE or external FUNCTION in addition to the ENTRY point will prevent the problem from occurring. The following program example illustrates the solution:

      i=0
      call sub(i)
      end

      subroutine sub(i)
      entry entersub(i)
      i=0
      i=i+1
      write(*,*) i
      end