Microsoft KB Archive/67420

= FIX: F1001: omf_ms.c:1.118, line 2785; Common Block Too Large =

Article ID: 67420

Article Last Modified on 12/1/2003

-

APPLIES TO


 * Microsoft FORTRAN Compiler 5.0
 * Microsoft FORTRAN Compiler 5.1
 * Microsoft FORTRAN Compiler 5.0
 * Microsoft FORTRAN Compiler 5.1

-



This article was previously published under Q67420



SYMPTOMS
When the data in a COMMON block exceeds 45,940,736 (44,864K) bytes, the Microsoft FORTRAN version 5.0 compiler generates the following error:

fatal error F1001: Internal Compiler Error

(compiler file '@(#)omf_ms.c:1.118', line 2785)

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

fatal error F1001: Internal Compiler Error

(compiler file '@(#)omf_ms.c:1.119', line 2787)



RESOLUTION
Although using a slightly smaller amount of data allows compilation, using this much data in a single module will violate other limitations of the FORTRAN compiler and linker. For example, decreasing the size of the INTEGER array in the above code sample allows compilation with FORTRAN 5.0, but generates the following linker error:

fatal error L1047: too many group, segment, and class names in one module

The only practical solution is to decrease the size of the arrays significantly. The largest quantity of data that does not violate the limits on the number of group, segment, and class names is 15,990,784 bytes, or 244 segments of 64K bytes per segment.



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 following code generates this error: INTEGER*1 A(45940737) COMMON A       END Any combination of data that adds up to more then 44,864K bytes will generate this error. The COMMON block can be named or unnamed.

The following is another code sample that generates this error: REAL*4 A(3388,3388) INTEGER*1 B(26561) COMMON /TEST/ A,B END

Additional query words: 5.00 5.10

Keywords: kbfix KB67420

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.