致命错误C1001：内部编译器错误（编译器文件'f：\vs70builds \ 3077 \vc \ Compiler \Utc \SCr\P2 \ main.c'，第148行） [英] fatal error C1001: INTERNAL COMPILER ERROR (compiler file 'f:\vs70builds\3077\vc\Compiler\Utc\src\P2\main.c' , line 148)
问题描述
嗨伙计们，
我希望这是这些事情的正确组合，如果没有道歉。
我已经得到一个奇怪的编译错误。它看起来类似于知识库文章320004中描述的问题
，除了特别的问题是在.NET 2003中修复了
，根据文章。
我得到的错误是：
致命错误C1001：INTERNAL COMPILER ERROR（编译器文件
''f：\ vs70builds \ 3077 \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ C ++
帮助菜单，或打开技术支持帮助文件获取更多信息
如果我按照320004中列出的步骤进行操作，＃pragma optimize （g，off）和受影响函数周围的
问题就会停止。
调试版本中没有显示错误，因此这似乎是一个优化错误。另外通常
和320004，还有一个while循环。我已经尝试重新安排代码
a bit没有运气，并且各种优化更改都没有解决它（bar
切换''全部关闭）。
我已经做了各种搜索，发现编译器错误引用了main.c的第146行
（主要是.NET 2002）和一堆引用148，其中一些是与throw / catch相关的
（这里不是这种情况）。
这段代码在VC6（SP5）下编译并运行正常。我们目前正在评估
我们的MSDN版本的.NET2003，并在两个版本下进行编译，以检查
在执行完整的
之前，所有内容在新编译器下仍能正常工作/>
升级。随着代码周围的#pragmas，代码仍然可以在两个版本的
下编译好，但我很好奇是否有一个修复可用于
这个问题或者是否存在还有更多细节吗？
干杯，
PufferFish。
Hi folks,
I hope that this is the correct group for these things, apologies if not.
I''ve got a strange compiler error. It appears to be similar to the issue
described in knowledgebase article 320004 except that particular problem was
fixed in .NET 2003, according to the article.
The error I get is:
fatal error C1001: INTERNAL COMPILER ERROR (compiler file
''f:\vs70builds\3077\vc\Compiler\Utc\src\P2\main.c'' , line 148)
Please choose the Technical Support command on the Visual C++
Help menu, or open the Technical Support help file for more information
If I follow the steps outlined in 320004, #pragma optimize("g", off) and on
around the affected function the problem stops. The error does not show in
debug builds, so this appears to be an optimisation error. Also in common
with 320004, there is a while loop involved. I''ve tried rearranging the code
a bit with no luck, and various optimisation changes didn''t fix it (bar
switching ''em all off).
I''ve done various searches and found compiler errors that refer to line 146
(mostly .NET 2002) of main.c and a bunch referring to 148, some of which are
related to throw/catch (which is not the case here).
This code compiled and ran OK under VC6 (SP5). We''re currently evaluating
our MSDN version of .NET2003 with compiles under both versions to check that
everything still works OK under the new compiler before doing a full
upgrade. With the #pragmas around the code, the code still compiles OK under
both versions but I was curious as to whether there is a fix available for
this problem or if there are any more details?
Cheers,
PufferFish.
推荐答案
您可以提供有问题的第148行及其上下文，以便我们可以实际知道发生了什么。您似乎也选择了
不正确的优化选项。你为什么不提供命令行
你用来编译代码。
ben
You may supply the problematic line 148 and its context so that we can
actually know what is going on. It also appears that you may have selected
incorrect optimization options. Why don''t you also supply the command line
you used to compile the code.
ben
嗨大家好，
我希望这是这些事情的正确组合，如果没有道歉。
我有一个奇怪的编译器错误。它看起来类似于知识库文章320004中描述的问题，除了特殊问题
在.NET 2003中得到修复，根据文章。
我得到的错误是：致命错误C1001：内部编译器错误（编译器文件）：'f：\ vsvs70builds \ 3077 \ vc \ Compiler \ Utc \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ main.c''，第148行
请在Visual C ++
帮助菜单中选择技术支持命令，或打开技术支持帮助文件以获取更多信息
如果我按照320004中列出的步骤，＃pragma optimize（" g"，off）和受影响的函数周围的
，问题就会停止。在调试版本中没有显示错误，因此这似乎是一个优化错误。与320004一样，有一个while循环。我已经尝试重新安排
代码而没有运气，并且各种优化更改并没有解决它（bar
切换它们全部关闭）。
我已经完成了各种搜索，发现编译器错误引用了main.c的行
146（主要是.NET 2002）和一堆引用148，其中一些
与throw / catch相关（这不是这种情况）。
此代码在VC6（SP5）下编译并运行正常。我们目前正在评估我们的MSDN版本的.NET2003，并在两个版本下进行编译，以检查
，在进行完整的升级之前，所有内容在新编译器下仍能正常工作。使用代码周围的#pragmas，代码仍会在两个版本下编译OK
，但我很好奇是否有可用于此问题的修复程序或是否有更多详细信息？
干杯，
PufferFish。
Hi folks,
I hope that this is the correct group for these things, apologies if not.
I''ve got a strange compiler error. It appears to be similar to the issue
described in knowledgebase article 320004 except that particular problem was fixed in .NET 2003, according to the article.
The error I get is:
fatal error C1001: INTERNAL COMPILER ERROR (compiler file
''f:\vs70builds\3077\vc\Compiler\Utc\src\P2\main.c'' , line 148)
Please choose the Technical Support command on the Visual C++
Help menu, or open the Technical Support help file for more information
If I follow the steps outlined in 320004, #pragma optimize("g", off) and on around the affected function the problem stops. The error does not show in
debug builds, so this appears to be an optimisation error. Also in common
with 320004, there is a while loop involved. I''ve tried rearranging the code a bit with no luck, and various optimisation changes didn''t fix it (bar
switching ''em all off).
I''ve done various searches and found compiler errors that refer to line 146 (mostly .NET 2002) of main.c and a bunch referring to 148, some of which are related to throw/catch (which is not the case here).
This code compiled and ran OK under VC6 (SP5). We''re currently evaluating
our MSDN version of .NET2003 with compiles under both versions to check that everything still works OK under the new compiler before doing a full
upgrade. With the #pragmas around the code, the code still compiles OK under both versions but I was curious as to whether there is a fix available for
this problem or if there are any more details?
Cheers,
PufferFish.
" benben" <是****** @ yahoo.com.au>在消息中写道
新闻：％2 **************** @ TK2MSFTNGP09.phx.gbl ...
"benben" <be******@yahoo.com.au> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
你可以提供有问题的第148行及其背景，以便我们能够真正知道发生了什么。您似乎也可能选择了不正确的优化选项。为什么你也不提供命令行
你用来编译代码。
You may supply the problematic line 148 and its context so that we can
actually know what is going on. It also appears that you may have selected
incorrect optimization options. Why don''t you also supply the command line
you used to compile the code.
非常感谢您的回复。 148行表示行148。不在我的代码中; F驱动器我没有
。它指的是Microsoft的Visual C源代码库;所以main.c
和错误是有关系的。如果你把实际的错误字符串
粘贴到google中，你会看到我的意思。
实际代码的一行是：
if（（ERT_INFO == type）&&（op_flags [EHFL_SUPRESSINFO]））
return（false）;
....这显然是无害的。所以其他地方的其他东西是
设置这一点。我无法将其提取到一个单独的
代码库中，该代码库专门导致错误发生。
编译命令行是：
/ O2 / D" NDEBUG" / DWIN32 / D" _WINDOWS" / D_MBCS / FD / EHsc / MT / J
/YX" stdafx.h" /Fp".\Release/cerrtest.pch" /Fo".\Release/" /Fd".\Release/"
/FR".\Release/" / W3 / nologo / c / Zi
PufferFish。
Hi,
Many thanks for your response. The "line 148" isn''t in my code; I don''t have
an F drive. It refers to Microsoft''s source base for Visual C; so the main.c
and the error is connected with that. If you paste the actual error string
into google, you''ll see what I mean.
The line of actual code that bails this is:
if ( (ERT_INFO == type) && (op_flags[EHFL_SUPRESSINFO]) )
return (false);
.... which is clearly mighty harmless. So something else somewhere else is
setting this up to happen. I''ve not been able to distill it into a separate
code-base that specifically causes the error to occur.
The compilation command line is:
/O2 /D "NDEBUG" /D "WIN32" /D "_WINDOWS" /D "_MBCS" /FD /EHsc /MT /J
/YX"stdafx.h" /Fp".\Release/cerrtest.pch" /Fo".\Release/" /Fd".\Release/"
/FR".\Release/" /W3 /nologo /c /Zi
PufferFish.
PufferFish写道：
PufferFish wrote:
致命错误C1001：内部编译器错误（编译器文件
''f：\vs70builds \\\\\\\\\\\\\\\\\\\\\\\ 148）
此代码在VC6（SP5）下编译并运行正常。我们目前正在评估我们的MSDN版本的.NET2003，并在两个
版本下进行编译，以便在进行完全升级之前检查新的
编译器下的所有内容是否仍然正常。使用围绕
代码的#pragmas，代码仍然可以在两个版本下编译好，但我很好奇是否有针对此问题的修复程序，或者是否还有更多详细信息？
fatal error C1001: INTERNAL COMPILER ERROR (compiler file
''f:\vs70builds\3077\vc\Compiler\Utc\src\P2\main.c'' , line 148)
This code compiled and ran OK under VC6 (SP5). We''re currently
evaluating our MSDN version of .NET2003 with compiles under both
versions to check that everything still works OK under the new
compiler before doing a full upgrade. With the #pragmas around the
code, the code still compiles OK under both versions but I was
curious as to whether there is a fix available for this problem or if
there are any more details?
VS.NET 2003没有已发布的错误修复程序。可能有一个针对此特定ICE的修补程序
，但是你''必须联系产品支持
才能找到 - 只有PSS可以提供修补程序。
-cd
There are no published bug fixes for VS.NET 2003. There may be a hotfix
available for this particular ICE, but you''d have to contact product support
to find out - only PSS can give out hotfixes.
-cd
这篇关于致命错误C1001：内部编译器错误（编译器文件'f：\vs70builds \ 3077 \vc \ Compiler \Utc \SCr\P2 \ main.c'，第148行）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
