Lahey/Fujitsu Fortran 95 (PRO, Standard, Express) v5.5 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.50j patch program (1.9 MB). Last updated 4/28/00.
    The downloaded file Patch55j.exe should be 2,007,976 bytes.
    Note: This is the final v5.5 patch.
  • LF95 v5.5 Release Notes Please read this before downloading and installing the update program.
  • LF95 v5.5 Bug Fix Descriptions of bugs fixed in the maintenance updates.

Lahey/Fujitsu Fortran 95 v5.5 Release Notes

The following descriptions are cumulative.

Version 5.50j

  • See LF95 v5.5 Bug Fix Descriptions.
  • Version 5.50i

  • Source for LF90 sequential unformatted file to LF95 format converter
    SRC\SEQUNF.F90 has been improved to explicitly calculate the size of the trailing RLI (record length indicator) from readily available data, and then performs a sanity check to make sure that the RLI is the size that it claims to be.
  • Source for optimum blocksize analyzer
    SRC\TRYBLK.F90 has been enhanced to explore some of the faster means of doing I/O. Specifically, it now tests the unformatted sequential I/O type, which may be at least twice as fast as the next fastest I/O method under Windows, and can be 4 - 10 times as fast as other I/O methods.
  • See LF95 v5.5 Bug Fix Descriptions.
  • Version 5.50h

  • Traceback data stored in exe
    If the options -NTRACE -NG -NCHK -NCOVER are in effect, the traceback line number information (COFF symbol table) will not be stored in the exe file. This will make an exe file smaller relative to the amount of lines in the source code.
  • Resource compiling
    Specifying only a resource file (*.RC) on the LF95 command line with the -C option results in the creation of a linkable .RES file.
  • Fujitsu C runtime
    The execution speed of the STRNCPY function has been improved. The improvement will be apparent when either linking with the FCC command or linking with the LF95 command (Fortran with C object).
  • VSW window title
    When displaying a window with an application built with the -VSW option (Very Simple Windows), the window title can be defined by setting the environment variable FORTVSWTITLE to the desired text.
  • See LF95 v5.5 Bug Fix Descriptions.
  • Version 5.50g

  • See LF95 v5.5 Bug Fix Descriptions.
  • Version 5.50f

  • See new entry below, under "Version 5.50a & 5.50b", "Module incompatibility".
  • See LF95 v5.5 Bug Fix Descriptions.
  • Version 5.50e

  • Improvement in compilation speed and memory usage
    You may see an improvement in compilation speed and a decrease in use of memory resources when compiling code with nested modules.
  • List-directed and namelist output
    List-directed and namelist output of a real constants of zero value will now be output with E-notation, per the Fortran 95 Standard. The 'E' character will now be output on values greater than or equal to 1.0E+100 (previously the 'E' was missing).
  • Runtime error messages documentation
    The file RTERRMSG.TXT that contains LF95 runtime error message iostat/stat numbers and the corresponding message text has been added in the LF95 installation directory.
  • Committed memory reduced for OPENing a file
    At runtime, when a file is opened, about 59 bytes of memory are allocated for the life of the application. Previously this was 125 bytes. This may impact applications that have large number of OPENs.
  • See LF95 v5.5 Bug Fix Descriptions.
  • Version 5.50d

  • See LF95 v5.5 Bug Fix Descriptions.
  • Version 5.50c

  • RANDOM_NUMBER subroutine
    The RANDOM_NUMBER subroutine execution speed has been improved.
  • Lahey ED Developer
    Installation of the Lahey ED Developer component into the same directory as an existing pre-v5.5 ED installation may not have had the personal configuration files updated. This would cause certain changes for v5.5 to not be available (e.g., the toolbar to invoke the Fujitsu Windows Debugger) . The v5.50c patch will rectify this if the Lahey ED Developer component is selected.
  • See LF95 v5.5 Bug Fix Descriptions.
  • Version 5.50a & 5.50b

  • Module incompatibility
    Modules compiled with v5.5 cannot be USEd by program units compiled with v5.0, or a severe compiler error will occur. Due to a module information enhancement made in v5.5, modules must be recompiled.

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

    The following descriptions are cumulative.

    Fixed in Version 5.50j

    • Some debug info is lost if a BLOCK DATA program precedes the main program in a file.
    • Invalid page fault on execution of particular code where the argument to ACHAR is an implied-do array.
    • Incorrect initialization of logical variable with -CHK -SAV options.
    • Internal compiler error on illegal array specification expression.
    • Internal compiler error on illegal duplicate subroutine and common block names.
    • List-directed output has an extraneous character for certain double precision variables.
    • Incorrect result for particular optimized (-O1) code.

    Fixed in Version 5.50i

    • Erroneous informational message, "is set but never used" when variable is the argument to UNDFL routine.
    • Subroutine's ENTRY arguments are not mapped correctly in particular optimized (-O1) code.
    • Incorrect result for particular optimized (-O1) code.
    • Incorrect compiler diagnostic message "Statement specified in WHERE statement or in WHERE construct must be an assignment statement".
    • Fujitsu debugger (FDB) hangs after giving a "Please wait to analyze debug information" message on Windows NT for source that calls the GINO library.
    • Calling the WiSK library routine WMenuRoot(0) to remove the root menu does not deactivate the associated accelerators.
    • The WiSK library routines WindowOpen and WindowOpenChild do not open non-centered windows with the status bars at the specified position.
    • In Lahey ED Developer, for source file pathnames containing long filenames, a new source window is opened each time the Previous/Next Error button is pressed after a compile with errors.

    Fixed in Version 5.50h

    • No compiler diagnostic message for relocation address overflow.
    • Bad result from RANDOM_NUMBER with -QUAD option.
    • Visual Analyzer incorrectly reports subroutine calling information for particular source code.
    • The EXIT subroutine does not set the specified DOS error level.
    • The DIVCHK subroutine does not work with the -TRAP D option.
    • Internal compiler error in very large main program unit.
    • Incorrect compiler diagnostic on END INTERFACE statement for a defined operation.
    • Sometimes a terminal five digit is not rounded up on formatted output.
    • When the first WRITE in a program is FORMAT('1'), a form feed character is not being output.
    • In Lahey ED Developer, an error occurs when attempting to change the value in the "Align comments at column" field of the Language Options for Fortran.
    • Fixed in Fujitsu Windows Debugger (WinFDB)
      • In the Watch Window, if a variable name is mis-spelled and the "Add" button is pressed, nothing happens to indicate the error. At this point, one notices that new variables cannot be added, and variables already displayed will not update when stepping the program.
      • Variables that go out of scope continue to be displayed in the watch window. When this happens, the behavior is similar to what happens when adding mis-spelled or non-existent variables (above).
      • Derived-type arrays refuse to display in the watch window.
      • Derived type variables should display as one element per line in the watch window, rather than all elements on one line.
      • Arrays should display as one element per line in watch window, rather than all elements on one line. Array elements are sometimes separated by ":", while at other times they are separated by "|".
      • If the command "Program|Restart" is clicked at any time, the debug session cannot be made to continue. The only option is to exit the debugger and restart it.
      • If the debug session is "killed" by clicking "Debug|Kill", it cannot be restarted. The only option is to exit the debugger and restart it.
      • The "Input Command" tool should be more specific. It is unclear if this is used for entering a command line argument, Dos command, or FDB command.
    • Bug fix descriptions for Lahey Winteracter Starter Kit (WiSK)
      • The graphics area is now set correctly when a window is opened maximized (i.e. MaxWindow is specified to WindowOpen) and the graphics area is set to a sub-area of that window.
      • WindowOpen and WindowOpenChild now center the window correctly. Previously the centering was based on the height of the useable area, not the total size of the window. This caused windows to be positioned too far down the screen and slightly to the right.
      • WMenuItemDelete now redraws the menu properly when a top-level item is deleted.
      • The default limit on the amount of text which can be entered into a string field is now 32K (or 64K for a multi-line field) as documented. Previously the actual default limit was 30000 characters for both types of string field.
      • WDialogGetCheckBox now sets the documented error code if called for a non-existent field or a field of the wrong type.
      • WDialogGetString now sets the documented error code if called for a non-existent field.
      • Calling WDialogSetField when the current dialog is a child dialog which has not been displayed now has no effect, in the same way as for a popup dialog. Previously the child dialog was shown at its current position.
      • IGrPolygonComplex now fills correctly when the current fill style is set to 1 (hatched in a single direction) and the hatching angle is set to 4 (vertical lines). Previously, this combination gave a cross-hatched fill.
      • The screen palette is now updated to match the graphics palette when switching to a Winteracter application from another application on 256 color screens. Previously if the application being switched from used a significantly different palette and the change of application did not also cause an Expose message then the wrong colors could be displayed.
      • A bug in Windows 95 and 98 which sometimes caused status bars to be redrawn incorrectly when resizing windows has been worked around. This problem did not affect programs running under NT or Win32s.
      • Graphics output now works correctly after closing a child window which was not the current output window. Previously graphics output would be corrupted in unpredictable ways until the next call to WindowSelect or WindowOpenChild.
      • A rare problem with Expose messages under Windows 9x in 256 color video modes has been fixed. Sometimes, the palette would appear to change and/or subsequent graphics would appear in a different window.
      • Common dialogs now work immediately after closing an inside root child window. In versions 2.10 to 2.10e the common dialog would fail if there had been no calls to WMessage, WMessagePeek or WindowOpenChild since the child window was closed.
      • WMenuGetState now works reliably after attempting to get the state of a non-existent menu option. Previously subsequent valid menu options could be reported as non-existent and an error code set.
      • Alt+Underlined Letter combinations can be now be used to access items in the root menu when an inside root child window has the input focus and the child window has a system menu.

    Fixed in Version 5.50g

  • Internal compiler error on DATA statement containing a repeat factor with -LONG option.
  • IF statement inside DO loop is not executed in particular optimized (-O1) code.
  • Debuggers do not display the correct value for an EQUIVALENCEd variable compiled with -G and -SAV options.
  • Incorrect runtime array bound error for particular code with -CHK option.
  • FDATE and CTIME service routines return incorrect month name.
  • Fixed in Version 5.50f

  • Wrong numeric result from expression alike to 5.0*(5.0**3)*5.0 with -AP -O1 options.
  • NDPEXC() may cause incorrect results from subsequent double precision operations.
  • Fujitsu C Compiler will produce an incorrect object filename with "-G and -O filename.OBJ" options, where ".OBJ" is uppercase. Also, .fwd file is not put in specified directory with "-G and -O directory\filename.obj" options.
  • The Lahey Video Graphics Library (LVGL.F90) functions ISKEY and IXKEY always return a value of .true., regardless of whether or not a key was pressed.
  • Fixed in Version 5.50e

  • Runtime NDP exception messages publish the text "Error occurs at" with no location following.
  • Incorrect result on particular optimized (-O1) code in a DO block.
  • Internal compiler error when redundant modules are USEd.
  • List-directed and namelist output of real constants of zero value do not have E notation, per the Fortran 95 Standard; the 'E' is not output on values greater than or equal to 1.0E+100.
  • The error "fwdmerg:[error] ..." is produced and excessive time is taken when building an application with many source files in different directories with the -G option.
  • Warning of non-standard feature is erroneously published for non-standard routines (such as the RND function) with the -NF95 option.
  • Execution stops, but a runtime error message is not published when the TIME argument to the DATE_AND_TIME subroutine is not defined as at least 10 characters.
  • Fixed in Version 5.50d

  • Visual Analyzer does not produce the .q files when analyzing source code with an include file.
  • In a namelist, a space character inside the parenthesis of an array subscript is interpreted as a zero character.
  • Incorrect result on particular optimized (-O1) code containing DO block with nested CASE statement.
  • A warning of non-standard feature is not published for the GETCL subroutine with the -F95 option.
  • Fixed in Version 5.50c

  • Incorrect result on particular optimized (-O1) code containing DO block with nested IF statement.
  • If a format error occurs in a WRITE statement containing ERR=, the ERR= branch will not be taken, no runtime diagnostic will be published, no output from that WRITE will occur, and program execution will continue to the next statement.
  • Internal compiler error on illegal module interdependency.
  • No compiler diagnostic for illegal DEALLOCATE of pointer variable subobject with INTENT(IN) attribute.
  • Exception access violation occurs in FDB (Fujitsu debugger) on particular code after two CONTINUE commands.
  • Problems with display of defined type variables in the watch window in WinFDB (Fujitsu Windows Debugger).
  • Visual Analyzer repeats and misaligns some output text.

    Privacy Policy

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