Search

fatal error C1001: An internal error has occurred in the compiler. by _lee

Closed
as Fixed Help for as Fixed

1
0
Sign in
to vote
Type: Bug
ID: 675321
Opened: 6/14/2011 7:12:05 AM
Access Restriction: Public
Moderator Decision: Sent to Engineering Team for consideration
0
Workaround(s)
0
User(s) can reproduce this bug
Following Simple code crashed C++ compliler with
" fatal error C1001: An internal error has occurred in the compiler."
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling version

Visual Studio 2010 SP1

Steps to reproduce

size_t length() { return 1; }
int glob = size_t(lenght() - 1);

Product Language

English

Operating System

Windows 7

Operating System Language

English

Actual results

aa.cpp(2) : fatal error C1001: An internal error has occurred in the compiler.
(compiler file 'msc1.cpp', line 1420)
To work around this problem, try simplifying or changing the program near the locations listed above.
Please choose the Technical Support command on the Visual C++
Help menu, or open the Technical Support help file for more information
Internal Compiler Error in C:\VS\VC\BIN\cl.exe. You will be prompted to send an error report to Microsoft later.

Expected results

error C3861: 'lenght': identifier not found
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 6/22/2011 at 11:12 AM
Hi:
    A fix for this issue has been checked into the compiler sources. The fix should show up in the next release of Visual C++.

Xiang Fan
Visual C++ Team
Posted by MS-Moderator07 [Feedback Moderator] on 6/14/2011 at 6:20 PM
Thank you for submitting feedback on Visual Studio 2010 and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by MS-Moderator01 on 6/14/2011 at 7:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.