BUG: Compiling With -4Ya -Ox -4fps1 Causes Stack Corruption

Last reviewed: February 29, 1996
Article ID: Q147760
The information in this article applies to:
  • Microsoft Fortran PowerStation for Windows 95 and Windows NT, version 4.0

SYMPTOMS

An application that is compiled with the -4Ya -Ox -4fps1 compiler switches together causes stack data corruption at run time.

CAUSE

Multiple variables are being assigned to the same stack location.

RESOLUTION

Don't use these compiler switches together.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

The following code illustrates the problem:

Sample Code

C Compile options needed: -4Ya -Ox -4fps1

      INTEGER NUMBER, DIVSOR, QUOT, REM
      NUMBER = 5
      DIVSOR = 2
      CALL DIVIDE (NUMBER, DIVSOR, QUOT, REM)

      PRINT *, 'Quotient : ', QUOT
      PRINT *, 'Remainder: ', REM
      END

      SUBROUTINE DIVIDE (NUMBER,DIVSOR,QUOT,REM)
      INTEGER NUMBER, DIVSOR, QUOT, REM, Q
      Q = NUMBER/DIVSOR
      REM = NUMBER-DIVSOR*Q
      QUOT = Q
      END

The following program output is produced at run time:

Quotient :           1
Remainder:           0

The correct output should be:

Quotient :           2
Remainder:           1


Additional reference words: 4.00
KBCategory: kbprg kbbuglist
KBSubcategory: FORTLngIss


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 29, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.