Lahey/Fujitsu Fortran 95 (PRO, Standard) v5.0 maintenance update

The update program below will update the current version of your product to the latest maintenance release version. This is only for owners of the same numbered version of the product. To update, download the update program below and run it in Windows.

The maintenance version is the alpha character after the version number. It is displayed in the first line of the banner when the compiler is invoked, as well as in listing files. The update program will update your product from any previous maintenance version. The existing product must have been installed from the product CD with the Windows registry information still intact.

To digress to a previous version, the product must be reinstalled from the product CD, then the update program for the desired maintenance release could be run. (Saving downloaded updates is recommended for this purpose. Previous versions can also be  requested from

  • LF95 v5.00f patch program (1.6 MB). Last updated 3/15/99.
    The downloaded file Patch50f.exe should be 1,671,454 bytes.
    Note: This is the final v5.0 patch.
  • LF95 v5.0 Release Notes Please read this before downloading and installing the update program.
  • LF95 v5.0 Bug Fix Descriptions of bugs fixed in the maintenance updates.

  • Lahey/Fujitsu Fortran 95 v5.0 Release Notes

    The following descriptions are cumulative.

    Version 5.00f

  • See LF95 v5.0 Bug Fix Descriptions.
  • Version 5.00e

  • Mandatory recompile with v5.00e
    You must recompile your source code in the following conditions:
    1. If you compile a MODULE with v5.00e, you must recompile all program units that USE that MODULE.
    2. If you compile a MODULE with v5.00e, you must recompile all MODULEs that are USEd by that MODULE, or a severe compiler error will occur.
    Note: It is not necessary to recompile any source code compiled with an earlier version of LF95 if the above conditions do not exist.
  • Fortran WinMain built-in
    A WinMain is now automatically provided when linking with the -WIN option (the driver will link with the LF95W.LIB library) that will call your LF95 main program. The previous suggestion to use a package like WiSK, Winteracter, RealWin, or GINO, solely for its WinMain module is no longer necessary.
  • File converter program
    The source code for a program to convert Lahey-Fujitsu (LF95) sequential unformatted files to Lahey (LF90 or EM/32) style is now provided. The source file SRC\UNFSEQ.F90 must be built with the LF90 language system.
  • Service Subroutines' documentation
    The text file SERVICE.TXT is now provided that contains descriptions of LF95 service subroutines.
  • See LF95 v5.0 Bug Fix Descriptions.
  • Version 5.00d

  • Execution speed improvement
    For programs containing COMMONs which contain double-precision variables, you may see an improvement in execution speed due to a an enhancement to the linker (Phar Lap 386|LINK) that improves alignment of COMMONs.
  • See LF95 v5.0 Bug Fix Descriptions.
  • Version 5.00c

  • See LF95 v5.0 Bug Fix Descriptions.

  • Lahey/Fujitsu Fortran 95 v5.0 Bug Fix Descriptions

    The following descriptions are cumulative.

    Fixed in Version 5.00f

  • Incorrect UNDEFINED message is issued for TO= array argument of MVBITS when -CHK is specified.
  • Internal compiler error on particular source code with -o1 only.
  • Compiling with -WIN and -ML WINAPI along with the -CHK option generates linker errors: Undefined symbol "_MODULE@win32mod_" ...
  • Execution quits on second iteration of loop that will eventually produce integer overflow with -o1 only.
  • Tab in column 1 prevents analysis (.Q file not created) in Visual Analyzer.
  • Fixed in Version 5.00e

  • A page fault occurs when executing a program containing WiSK calls.
  • A page fault occurs when executing a program created with the -VSW (Very Simple Windows) option.
  • Compiler issues incorrect severe error message on USE of MODULE containing "INTRISIC kind" statement.
  • A scratch file closed with STATUS= 'KEEP' is not saved.
  • END= branch is not taken when READing EOF on a file opened as ACCESS= 'TRANSPARENT'.
  • Backslash in FORMAT statement does not suppress <CR><LF>.
  • CALL SYSTEM with DOSBOX= .FALSE. does not execute command.
  • Bad syntax in FORMAT statement in the form of "2$i3" causes an access violation.
  • Object and subsequent exe file are oversized for a MODULE containing a DATA statement.
  • Redirected output omits blank lines.
  • Value of index variable after exiting DO block is incorrect with -O1 option.
  • Visual Analyzer analysis ends abnormally with an error when linker option -LIBPATH is specified.
  • Incorrect runtime error stating an uninitialized argument variable occurs on call to GETCL subroutine with the -CHK option.
  • CALL ERROR subroutine does not generate traceback output.
  • FORMAT containing a zero value for w in a Fw.d format descriptor is sometimes outputting asterisks.
  • Reading followed by writing to a direct formatted file opened with STATUS= 'REPLACE' wastes a file handle.
  • READ I/O error occurs when reading a file opened with a BLOCKSIZE= value greater than or equal to 16K.
  • INQUIRE returns zero for FLEN on an open file.
  • Unformatted WRITE of an array greater than 16K bytes to a file opened as ACCESS= 'TRANSPARENT' does not write all data.
  • Program terminates on I/O statement containing IOSTAT= .
  • Call to WiSK routine WinfoWindow causes a linker error.
  • Internal compiler error on particular source code with -o1 only.
  • The debugger crashes when trying to set a breakpoint from the checkpoints box.
  • A trailing space character is added to unknown switches sent to the linker.
  • Internal compiler error with combination of USE, INCLUDE and MODULE definition following USE in source file.
  • Specifying the -WISK and -ML MSVC options cause a compiler error.
  • Linker error when path contains a dot (period) character.
  • Fixed in Version 5.00d

  • Access violation when executing an ALLOCATE statement in the form of this example:
    ALLOCATE( GRD(I)%A(2) ).
  • Wrong result when evaluating an array constructor in the form of this example:
    ( /( /( (1,2,I=1,1),3,4,I2= IU4V,1 )/ ),5/ ).
  • Internal compiler error on bad code where a kind parameter is used in the same statement that it is being declared.
  • Internal compiler error when compiling one source file with two modules each containing a module procedure of the same name.
  • Internal compiler error on the USE statement in a module with the ONLY attribute specifying an operator interface that has the same name as one in the current module.
  • Fixed in Version 5.00c

  • Incorrect message is issued for zero sized array with -CHK.
  • Output result of zero-sized MATMUL is incorrect.
  • Error should be severe for illegal assignment to DO loop variable.
  • Stack overflow calling TIME when program has GETTIM procedure defined.
  • Reading file opened with FORM= 'BINARY' will cause a page fault, in some cases.
  • Access violation on format string containing "$i".
  • Traceback missing when error is wrong data type for format edit descriptor.
  • IOSTAT_MSG not returning message text for ALLOCATE error.

    Privacy Policy

    © 2007-2022 Lahey Computer Systems, Inc. All Rights Reserved.
    Lahey Computer Systems, Inc., P.O. Box 6091, Incline Village, NV 89450 USA