Article ID: 104777
Article Last Modified on 12/1/2003
APPLIES TO
- Microsoft FORTRAN Compiler 4.0
- Microsoft FORTRAN Compiler 4.01
- Microsoft FORTRAN Compiler 4.1
- Microsoft FORTRAN Compiler 5.0
- Microsoft FORTRAN Compiler 5.1
- Microsoft FORTRAN Compiler 4.1
- Microsoft FORTRAN Compiler 5.0
- Microsoft FORTRAN Compiler 5.1
This article was previously published under Q104777
SYMPTOMS
Programs compiled with the $STORAGE:2 metacommand, the /4I2 option and $DEBUG metacommand, or the /4Yb option, with integer variables taking values beyond their full 16-bit range (-32,768 to 32,767), may not generate the following error:
CAUSE
The $STORAGE:2 metacommand, /4I2 option and $DEBUG metacommand, or the /4Yb option does not cause the compiler to generate additional code that will lead to a jump to the overflow routine for integer values that are out of range. This incorrect code generation is due to the common subexpression elimination optimization.
RESOLUTION
To correctly generate this error message for integer values that are out of the integer*2 (16-bit) range, compile with the /Od switch to disable optimization. Optimization may be partially turned back on with the optimization switches: /Os, /Ot, and /Ol (which do not enable common subexpression elimination /Oc).
STATUS
Microsoft has confirmed this to be a problem in FORTRAN versions 4.0, 4.01, 4.1, 5.0, and 5.1. This problem was corrected in FORTRAN PowerStation, version 1.0.
MORE INFORMATION
The following code does generate the F6099 error if compiled with the partial optimization of /Odlt, but will not generate the error if complied with either the default full optimization "/Ox" or common subexpression elimination "/Odc":
Sample Code
$debug
$storage:2
integer*2 i,j,k
i=10
j=4000
k=i*j
end
Additional query words: 4.00 4.01 4.10 5.00 5.10 buglist4.00 buglist4.01 buglist4.10 buglist5.00 buglist5.10 fixlist1.00
Keywords: kbbug kbfix KB104777
