Search

Downloads

 

Lahey/Fujitsu Fortran 95 (PRO, Standard, Express) v5.7 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 support@lahey.com.)

  • LF95 v5.70f update program (3.8 MB). Last updated 04/23/04.
    The downloaded file Patch57f.exe should be 3,924,746 bytes.
  • LF95 v5.70f update program for 3 1/2 inch high density (1.44 MB) floppy diskettes.
  • LF95 v5.7 Release Notes Please read this before downloading and installing the update program.
  • LF95 v5.7 Bug Fix Descriptions of bugs fixed in the maintenance updates.
  • Projected release date for next update:  Undetermined.

  • Lahey/Fujitsu Fortran 95 v5.7 Release Notes

    The following descriptions are cumulative.

    Version 5.70f

  • See LF95 v5.7 Bug Fix Descriptions.
  • Automake
    The v5.70f update only fixes one issue with Automake that was introduced in the v5.70e update. The Express edition was not affected and does not need installation of this update if the v5.70e update is installed.
  • Version 5.70e

  • See LF95 v5.7 Bug Fix Descriptions.
  • New -CONCC compiler option
    Specify -nconcc to turn off Fortran carriage control processing for console I/O.
  • Binary (transparent) file size limit
    The limit on external binary file size has been removed (increased from 2 gigabytes to more than 18 exabytes, i.e., from 2**31-2 to 2**64-2 bytes). Note that the maximum number of records is 2,147,483,647.
  • Namelist comments
    Product suggestion to allow LF95 to accept comments included in a namelist to start in columns other than one, when the comment is the only syntax on a given line.
  • Automake
    The single limit of 200 sections/source files is now replaced by 2 limits of 2000 sections and 2 MBytes for the total size of text in COMPILE=, OBJDIR=, OBJEXT=, INCLUDE=, SYSINCLUDE= and CHECK= directives (including any implied from previous sections).
  • Version 5.70d

  • See LF95 v5.7 Bug Fix Descriptions.
  • -LST compiler option
    The base filename for the listing file is created from the first source filename on the command line, rather than the last filename.
  • PDF manuals
    Updated revisions of the Language Reference and User's Guide are available for download.
  • Version 5.70c

  • See LF95 v5.7 Bug Fix Descriptions.
  • PDF manuals
    Updated revisions of the Language Reference and User's Guide are available for download.
  • Version 5.70b

  • See LF95 v5.7 Bug Fix Descriptions.
  • File size limit
    The limit on external file size has been removed (increased from 4 gigabytes to more than 18 exabytes, i.e., from 2**32-2 to 2**64-2 bytes).
  • Preconnected Unit=*
    Changing preconnected units 5 and 6 will no longer affect unit=*. For example, if unit 5 (stdin) or 6 (stdout) are connected to a file, unit=* can be used to read from the keyboard and write to the console.
  • Winteracter
    This update will install the import libraries necessary for the proper operation of Winteracter when the WiSK component is not installed from the v5.7 CD.

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

    The following descriptions are cumulative.

    Fixed in Version 5.70f

    • Automake.exe erroneously has a dependency on KeyLbE32.dll (introduced in v5.70e).

    Fixed in Version 5.70e

    • Access violation if subroutine compiled with -chk and main compiled with -nchk.
    • Access violation on internal WRITE to character array.
    • Incorrect result from internal file write with -chk.
    • An optional dummy argument associated with an absent actual argument is treated as a zero-length dummy argument.
    • Incorrect result from the ALLOCATED function for a derived type allocatable array with the SAVE attribute when re-entering a subprocedure.
    • Cannot REWIND files OPENed with ACTION='WRITE'.
    • The output buffer is not flushed when an I/O error occurs.
    • Incorrect result (lost precision) for quad precision arithmetic with -o0.
    • A dialog box is produced on the STOP statement if the executable is invoked via the PATH environment variable.
    • Incorrect result when array subscripts are used for namelist input.
    • Runtime error should be an underflow on floating point input data that is smaller than the range of the data type.
    • Runtime error on WRITE statement with combination of T format editing and ADVANCE='NO'.
    • The first character is used for carriage control but in subsequent WRITE statements with ADVANCE='NO' it is not.
    • Fujitsu Sampler Tool does not calculate the function costs on Windows XP.
    • Fujitsu Visual Analyzer prints only the portion of the Call Graph that fits on the first page when Focus is selected.
    • WiSK Resource Editor's Settings|Preferences menu option is not functional.
    • WiSK Winteracter module is missing the DrawableDialog parameter.

    Fixed in Version 5.70d

    • Incorrect results of array of derived type with -o0.
    • Internal compiler error when initializing derived type component with binary constant.
    • Runtime exception when accessing pointer function result.
    • Internal compiler error calling module pointer function.
    • Internal compiler error with -xref option.
    • IOSTAT_MSG does not return text for error status code 1116.
    • IOSTAT is not set if REWIND is used on an TRANSPARENT access file.
    • Incorrect diagnostic "<function> shall be declared as a function in a host or module scoping unit." when function is declared as ML_EXTERNAL.
    • Incorrect results with -chkglobal.
    • No diagnostic for ambiguous generic procedure with optional arguments.
    • Internal compiler error on included subroutine segment.
    • Internal compiler error on INQUIRE output-item of derived type with a union.
    • No diagnostic on list-directed input of incorrect complex number.
    • Runtime exception on 4098 writes of carriage control character 1 or 0.
    • Incorrect diagnostic on character array structure constructor.
    • Fujitsu C compiler hangs or aborts when the INCLUDE environment variable contains a pathname with a trailing backslash.
    • WiSK
      • A workaround has been implemented for a Windows XP bug which causes resizing of a window to be handled incorrectly when using the 'Windows XP' theme and the 'show window contents while dragging' effect. Under these conditions increasing the size of a window reported an Expose message instead of a Resize message and Winteracter's internal window dimensions were not updated, resulting in incorrectly scaled graphics. This problem did not occur with the 'Windows Classic' theme selected or with the 'show window contents while dragging' effect turned off.
      • Programs generated by the Application Wizard no longer have spurious pre-processing for the program icon in the generated resource script.
      • The skeleton demo now assigns MESSAGE%TIME to ITIME rather than the obsolete MESSAGE%VALUE2 which is no longer supported.
      • The resource format documentation for label fields in the on-line help file has been corrected to show SS_LEFTNOWORDWRAP as the style for fields with word wrap disabled rather than SS_SIMPLE.
      • The codes which are returned for unshifted and shifted function keys in LVGL are slightly wrong.
      • The call to WindowFontStyle has been replaced with a suitable call to WindowFont in LVGL.
    • WiSK Resource Editor
      • The error message generated by the resource editor in the rare case when it is unable to generate the Fortran symbol header file, has been corrected.
      • The resource editor now prevents entry of an identifier and other irrelevant properties when the 'Separator' checkbox is selected for a menu item. Similarly the 'Separator' option is greyed when any of 'Popup', 'Checked' or 'Greyed' are selected.
      • When editing the properties of an image which cannot itself be edited in the resource editor moving the properties dialog no longer corrupts the display if the resource being edited is not also an image.
      • A potential access violation error has been eliminated when cutting and pasting menu items in the resource editor.
      • When "No wrap" is selected for a label field, the resource editor no longer treats the field as a picture/frame, the next time the field is reloaded.
    • WiSK WINTERACTER module
      • The formal name of the option strings array in the WDialogPutMenu interface definition has been corrected from OPTIONS to OPTION.
      • The formal name of the default button argument WMessageBox interface definition has been corrected from IDEF to IDEFBUT.

    Fixed in Version 5.70c

    • Use of EXTERNAL in an INTERFACE generates incorrect compiler error.
    • FORALL construct causes memory leak.
    • Internal compiler error when module file is not found.
    • Incorrect result with Fortran 200x allocatable.
    • Internal compiler error when type dclaration is missing.
    • An incorrect "END DO" statement causes the compiler to hang.
    • Internal compiler error when generic module procedure name is used in an attribute expression.
    • Messages are incorrectly placed.
    • USE ONLY attribute generates incorrect compiler error.
    • Result of overflowed long integer multiplication does not retain the low order bits.
    • Automake's plusfort.fig license file is not found if pathname is longer than 64 characters.

    Fixed in Version 5.70b

    • Using the OPEN statement and specifying unit=* might generate a runtime error when a subsequent WRITE is attempted to unit=*.