FIX: F1001: XX-2 line 539, Allocating 43 Arrays in 1 Statement

Last reviewed: September 11, 1997
Article ID: Q67231

5.00 5.10 | 5.00 5.10

MS-DOS    | OS/2

kbtool kbfixlist kbbuglist kberrmsg

The information in this article applies to:

Microsoft FORTRAN for MS-DOS, versions 5.0 and 5.1
Microsoft FORTRAN for OS/2, versions 5.0 and 5.1

SYMPTOMS

When you allocate 43 or more arrays with one ALLOCATE statement in Microsoft FORTRAN version 5.0, the following error is produced, where XX = ASCII characters 2 and 254:

   fatal error F1001:  Internal Compiler Error
   (compiler file "XX-2," line 539)

With Microsoft FORTRAN version 5.1, the following error is produced:

   fatal error F1001:  Internal Compiler Error
   (compiler file '', line 404)

RESOLUTION

Breaking the ALLOCATE statement into two separate statements eliminates the error.

STATUS

Microsoft has confirmed this to be a problem in FORTRAN versions 5.0 and 5.1. This problem was corrected in FORTRAN PowerStation.

MORE INFORMATION

The size of the arrays has no effect on the error. If only 42 arrays are defined and allocated, the error is not generated.

The following code reproduces the internal compiler error:

      INTEGER
     + a1  [ALLOCATABLE] (:), a2  [ALLOCATABLE] (:),
     + a3  [ALLOCATABLE] (:), a4  [ALLOCATABLE] (:),
     + a5  [ALLOCATABLE] (:), a6  [ALLOCATABLE] (:),
     + a7  [ALLOCATABLE] (:), a8  [ALLOCATABLE] (:),
     + a9  [ALLOCATABLE] (:), a10 [ALLOCATABLE] (:),
     + a11 [ALLOCATABLE] (:), a12 [ALLOCATABLE] (:),
     + a13 [ALLOCATABLE] (:), a14 [ALLOCATABLE] (:),
     + a15 [ALLOCATABLE] (:), a16 [ALLOCATABLE] (:),
     + a17 [ALLOCATABLE] (:), a18 [ALLOCATABLE] (:),
     + a19 [ALLOCATABLE] (:), a20 [ALLOCATABLE] (:),
     + a21 [ALLOCATABLE] (:), a22 [ALLOCATABLE] (:),
     + a23 [ALLOCATABLE] (:), a24 [ALLOCATABLE] (:),
     + a25 [ALLOCATABLE] (:), a26 [ALLOCATABLE] (:),
     + a27 [ALLOCATABLE] (:), a28 [ALLOCATABLE] (:),
     + a29 [ALLOCATABLE] (:), a30 [ALLOCATABLE] (:),
     + a31 [ALLOCATABLE] (:), a32 [ALLOCATABLE] (:),
     + a33 [ALLOCATABLE] (:), a34 [ALLOCATABLE] (:),
     + a35 [ALLOCATABLE] (:), a36 [ALLOCATABLE] (:),
     + a37 [ALLOCATABLE] (:), a38 [ALLOCATABLE] (:),
     + a39 [ALLOCATABLE] (:), a40 [ALLOCATABLE] (:),
     + a41 [ALLOCATABLE] (:), a42 [ALLOCATABLE] (:),
     + a43 [ALLOCATABLE] (:)

      ALLOCATE (
     + a1  (1), a2  (1), a3  (1), a4  (1), a5  (1),
     + a6  (1), a7  (1), a8  (1), a9  (1), a10 (1),
     + a11 (1), a12 (1), a13 (1), a14 (1), a15 (1),
     + a16 (1), a17 (1), a18 (1), a19 (1), a20 (1),
     + a21 (1), a22 (1), a23 (1), a24 (1), a25 (1),
     + a26 (1), a27 (1), a28 (1), a29 (1), a30 (1),
     + a31 (1), a32 (1), a33 (1), a34 (1), a35 (1),
     + a36 (1), a37 (1), a38 (1), a39 (1), a40 (1),
     + a41 (1), a42 (1), a43 (1))
      END

To avoid this error, limit each ALLOCATE statement to less than 43 arrays.

Additional reference words: 5.00 5.10
KBCategory: kbtool kbfixlist kbbuglist kberrmsg
KBSubcategory: FLIss
Solution Type : kbfix

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 11, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.