The information in this article applies to:
- The Microsoft C/C++ Compiler (CL.EXE) included with:
- Microsoft Visual C++ for Windows, versions 1.5, 1.51
- Microsoft Visual C++, 32-bit Edition, versions 1.0, 2.0, 4.0, 4.1,
4.2, 5.0
SYMPTOMS
Compiling a .CPP file that includes a large amount of header file
information may cause the compiler to generate a C1001 error when
using the /Zg switch to generate function prototypes.
- In Visual C++ 32-bit edition, vesrion 5.0, the error message
may appear as:
fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 1188)
Please choose the Technical Support command on the Visual C++ Help menu,
or open the Technical Support help file for more information.
- In Visual C++ 32-bit edition, version 4.x (Compiler version
10.00), the error message may appears as:
fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 899)
Please choose the Technical Support command on the Visual C++ Help menu,
or open the Technical Support help file for more information.
- In Visual C++ 32-bit edition, version 2.0 (Compiler version 9.00),
the error message appears as:
fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 1056)
Please choose the Technical Support command on the Visual C++ Help menu,
or open the Technical Support help file for more information.
- In Visual C++ 32-bit edition, version 1.0 (Compiler version 8.00),
the error message appears as:
fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 602)
Please choose the Technical Support command on the Visual Workbench Help
menu, or open the Technical Support help file for more information.
- In Visual C++ for Windows, versions 1.5 and 1.51 (Compiler version
8.00c), the error message appears as:
fatal error C1001: internal compiler error
(compiler file 'msc1.cpp', line 585)
RESOLUTION
Avoid using /Zg with a large amount of header file information, such as the
MFC class library headers.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article. We are researching this bug and will post
new information here in the Microsoft Knowledge Base as it becomes
available.
|