KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q67355: Compiler May Hang Under DOS When Using /qc and Memory Runs Out

Article: Q67355
Product(s): See article
Version(s): 6.00 6.00a
Operating System(s): MS-DOS
Keyword(s): ENDUSER | buglist6.00 buglist6.00a | mspl13_c
Last Modified: 4-DEC-1990

Under certain circumstances, the compiler may run out of memory when
trying to compile a source module. In some situations, when both
compiling under DOS and specifying the /qc option to invoke the quick
compiler, an out-of-memory condition may result in garbage output
being dumped to the screen, or the following error may be generated:

   fatal error C1063: compiler limit : compiler stack overflow

Depending on the particular code being compiled and the optimizations
specified, the C1063 error may or may not contain any error text. In
some cases, only the error number is displayed and then the computer
hangs before the "compiler limit" message is displayed.

This problem has been observed only with the real-mode quick compile
option. Simplifying the code is one way to work around the problem.

Microsoft has confirmed this to be a problem in C versions 6.00 and
6.00a. We are researching this problem and will post new information
here as it becomes available.

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.