Metacommands & Options that Increase Executable File Size (60077)
The information in this article applies to:
- Microsoft FORTRAN Compiler for MS-DOS 4.0
- Microsoft FORTRAN Compiler for MS-DOS 4.01
- Microsoft FORTRAN Compiler for MS-DOS 4.1
- Microsoft FORTRAN Compiler for MS-DOS 5.0
- Microsoft FORTRAN Compiler for MS-DOS 5.1
- Microsoft FORTRAN compiler for OS/2 4.1
- Microsoft FORTRAN compiler for OS/2 5.0
- Microsoft FORTRAN compiler for OS/2 5.1
- Microsoft FORTRAN PowerStation for MS-DOS 1.0
- Microsoft FORTRAN PowerStation for MS-DOS 1.0a
- Microsoft Fortran Powerstation 32 for Windows NT 1.0
- Microsoft Fortran Powerstation 32 for Windows NT 4.0
This article was previously published under Q60077 SUMMARY
The various FORTRAN compile and link options affect the size of the
resulting executable file. Three compiler options can significantly
affect the amount of memory needed to run an application: the $DEBUG
metacommand or the /4Yb debugging compiler option switch, the /Zi
CodeView/Visual Workbench information compiler option switch, and the
$STORAGE:2 metacommand or the /4I2 integer size compiler option switch.
When Microsoft FORTRAN version 5.1 compiles an application with debug
information, the executable file contains up to 40 percent more code
than the same application without debugging information. In version
5.0, debug information increases the executable file size from 5 to 28
percent. The memory required to load the application increases by the
same amount. It appears that the size increase is even greater for
large and complex applications. In versions 4.0 and 4.1, the magnitude
of the increase is smaller, between 3 and 19 percent.
| Modification Type: | Major | Last Reviewed: | 12/1/2003 |
|---|
| Keywords: | kberrmsg kbLangFortran KB60077 |
|---|
|