16,551
社区成员
发帖
与我相关
我的任务
分享INTERNAL COMPILER ERROR
我用VC++ \SP6
写了个很简单的程序，结果报了个错误：
--------------------Configuration: CLIPBOARD - Win32 Debug--------------------
Compiling...
A.C
c:\myproject\A\A.c(4) : fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 1794)
Please choose the Technical Support command on the Visual C++
Help menu, or open the Technical Support help file for more information
Error executing cl.exe.
A.OBJ - 1 error(s), 0 warning(s)
求解！！！
写了个很简单的程序，结果报了个错误：
--------------------Configuration: CLIPBOARD - Win32 Debug--------------------
Compiling...
A.C
c:\myproject\A\A.c(4) : fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 1794)
Please choose the Technical Support command on the Visual C++
Help menu, or open the Technical Support help file for more information
Error executing cl.exe.
A.OBJ - 1 error(s), 0 warning(s)
求解！！！
...全文
请发表友善的回复…
发表回复
oyljerry 2005-07-30
- 打赏
- 举报
具体什么代码
weiasp 2005-07-30
- 打赏
- 举报
还是解决不了啊。
有没有哪位高人，能帮我解决这个问题。
这个问题以前没有出现过，就最近出现的。是不是少了个什么文件什么的。
有没有哪位高人，能帮我解决这个问题。
这个问题以前没有出现过，就最近出现的。是不是少了个什么文件什么的。
Kudeet 2005-07-12
- 打赏
- 举报
Q122042 BUG: Fatal Error C1001 Using /Zg with Large C++ Header Files
在MS KB里有几篇讲这个问题的文章，你再多查查
在MS KB里有几篇讲这个问题的文章，你再多查查
Kudeet 2005-07-12
- 打赏
- 举报
BUG: You may receive a "fatal error C1001: INTERNAL COMPILER ERROR" error message when template classes or template class header files are included in a precompiled header file
View products that this article applies to.
Article ID : 195738
Last Review : May 26, 2005
Revision : 3.0
This article was previously published under Q195738
On this page
SYMPTOMS
When template classes or template class header files are included in a precompiled header file, the compiler may generate the following error for files that use the precompiled header:
fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 1786)
-or-
fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 1188)
This error occurs only on machines with the Windows 95 or Windows 98 operating system.
Back to the top
CAUSE
The compiler exceeds the allocated memory limit.
Back to the top
RESOLUTION
Use one of the following three suggested workarounds: • Use compiler switch /Zm#nn to increase the compiler's heap memory allocation limit. The default value of #nn is 100 and the maximum value is 2000. Manually add this switch in Developer Studio: under the Project menu, click Setting, the click C/C++, then Project Options. Usually, a value of 1000 works.
NOTE: You may need to increase the system virtual memory to accommodate the increased #nn for /Zm.
• Remove the template class header files from the precompiled header file.
• Use "Automatic use of precompiled headers" (/YX switch), or, "Not using precompiled header."
Back to the top
STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
This problem was corrected in Microsoft Visual C++ .NET.
Back to the top
View products that this article applies to.
Article ID : 195738
Last Review : May 26, 2005
Revision : 3.0
This article was previously published under Q195738
On this page
SYMPTOMS
When template classes or template class header files are included in a precompiled header file, the compiler may generate the following error for files that use the precompiled header:
fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 1786)
-or-
fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 1188)
This error occurs only on machines with the Windows 95 or Windows 98 operating system.
Back to the top
CAUSE
The compiler exceeds the allocated memory limit.
Back to the top
RESOLUTION
Use one of the following three suggested workarounds: • Use compiler switch /Zm#nn to increase the compiler's heap memory allocation limit. The default value of #nn is 100 and the maximum value is 2000. Manually add this switch in Developer Studio: under the Project menu, click Setting, the click C/C++, then Project Options. Usually, a value of 1000 works.
NOTE: You may need to increase the system virtual memory to accommodate the increased #nn for /Zm.
• Remove the template class header files from the precompiled header file.
• Use "Automatic use of precompiled headers" (/YX switch), or, "Not using precompiled header."
Back to the top
STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
This problem was corrected in Microsoft Visual C++ .NET.
Back to the top
handwolf 2005-07-12
- 打赏
- 举报
按照一楼找的资料，试试
weiasp 2005-07-12
- 打赏
- 举报
我安装了SP6,还是不能解决这个问题。
Kudeet 2005-07-12
- 打赏
- 举报
Fatal Error C1001
INTERNAL COMPILER ERROR
(compiler file 'file', line number)
This error is most often generated in one of two cases:
Failure to recover the compiler's internal state following detection of a syntax error in the program. The first pass of the compiler will occasionally fail when attempting to recover its state following the detection of a malformed program. Typically, the compiler will have printed an error message (or messages) and will later produce an internal compiler error. In most cases, fixing the errors reported in your code and recompiling will solve the problem.
Failure of the code generator to find a way to generate correct code for a construct. This is most often caused by the interaction of an expression and an optimization option. The optimization has generated a tree which the compiler does not know how to handle. Such a problem can often be fixed by removing one or more optimization options when compiling the particular function containing the line indicated in the error message.
If no error messages have been emitted prior to the internal compiler error, then the next step is to determine which pass of the compiler is emitting the internal compiler error. This can be determined by recompiling the application with the /Bd option included. The /Bd option will cause each pass to print its name and arguments when it is invoked. The last pass invoked before the error is emitted is the one responsible.
If the pass indicated is P1, then the likely problem is still error recovery, as in number one above, but it is happening before the compiler has had a chance to emit the error message for the error it has just discovered. In such a case, examine the line on which the internal compiler error is reported. This line may also contain an unreported syntax error. Fixing any errors you find on that line will solve the internal compiler error in most cases. If you cannot find any error on that line or on the line previous to the one reported, contact Microsoft Product Support Services for help.
If the pass indicated is P2, then the problem can usually be fixed by removing one or more optimization options (or using a different code generator). You can determine which option is at fault by removing them one at a time and recompiling until the message goes away. Generally the last one removed is the problem and all other optimizations can be used safely. The most common culprits are /Og, /Oi, and /Oa. Once the offending optimization is discovered, it need not be turned off for the entire compilation. The offending optimization can be disabled with the optimize pragma while compiling the function where the error occurred, but enabled for the rest of the module.
More rarely, such errors occur at very low optimization levels or even when optimization is disabled. In such cases, rewriting the line where the error is reported (or possibly several lines including the one causing the error) may be a solution. If none of these options works, consult the technical support help file or the technical support section in one of your manuals.
msdn
有可能是VC有问题，记得好象是个BUG，装一个VC的SP6试试
INTERNAL COMPILER ERROR
(compiler file 'file', line number)
This error is most often generated in one of two cases:
Failure to recover the compiler's internal state following detection of a syntax error in the program. The first pass of the compiler will occasionally fail when attempting to recover its state following the detection of a malformed program. Typically, the compiler will have printed an error message (or messages) and will later produce an internal compiler error. In most cases, fixing the errors reported in your code and recompiling will solve the problem.
Failure of the code generator to find a way to generate correct code for a construct. This is most often caused by the interaction of an expression and an optimization option. The optimization has generated a tree which the compiler does not know how to handle. Such a problem can often be fixed by removing one or more optimization options when compiling the particular function containing the line indicated in the error message.
If no error messages have been emitted prior to the internal compiler error, then the next step is to determine which pass of the compiler is emitting the internal compiler error. This can be determined by recompiling the application with the /Bd option included. The /Bd option will cause each pass to print its name and arguments when it is invoked. The last pass invoked before the error is emitted is the one responsible.
If the pass indicated is P1, then the likely problem is still error recovery, as in number one above, but it is happening before the compiler has had a chance to emit the error message for the error it has just discovered. In such a case, examine the line on which the internal compiler error is reported. This line may also contain an unreported syntax error. Fixing any errors you find on that line will solve the internal compiler error in most cases. If you cannot find any error on that line or on the line previous to the one reported, contact Microsoft Product Support Services for help.
If the pass indicated is P2, then the problem can usually be fixed by removing one or more optimization options (or using a different code generator). You can determine which option is at fault by removing them one at a time and recompiling until the message goes away. Generally the last one removed is the problem and all other optimizations can be used safely. The most common culprits are /Og, /Oi, and /Oa. Once the offending optimization is discovered, it need not be turned off for the entire compilation. The offending optimization can be disabled with the optimize pragma while compiling the function where the error occurred, but enabled for the rest of the module.
More rarely, such errors occur at very low optimization levels or even when optimization is disabled. In such cases, rewriting the line where the error is reported (or possibly several lines including the one causing the error) may be a solution. If none of these options works, consult the technical support help file or the technical support section in one of your manuals.
msdn
有可能是VC有问题，记得好象是个BUG，装一个VC的SP6试试
