Internal error has occured in the compiler when compling opencv_lapack - by aqiruse

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 742715 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 5/18/2012 3:16:09 PM
Access Restriction Public


1>c:\opencv2.0\3rdparty\lapack\dlasq1.c(196): fatal error C1001: An internal error has occurred in the compiler.
1>  (compiler file 'f:\dd\vctools\compiler\utc\src\p2\main.c', line 211)
Sign in to post a comment.
Posted by Microsoft on 5/29/2012 at 10:19 AM
We have a fix for this bug, and we expect it to make it into Visual Studio 11. Thanks again for reporting this issue.
Posted by Microsoft on 5/22/2012 at 2:21 AM
We are able to repro this locally, and we are currently seeing if we can fix this for Visual Studio 11. So we don’t need a self-contained repro.
Posted by Microsoft on 5/21/2012 at 11:55 AM
Hi and thanks showing interest in trying out the Dev11 Beta and for taking the time to report this issue you have encountered. In order to expedite an investigate into this i will need a self-contained repro. The best way to do this is to generate a preprocessed file that generates the error. You can do this by simply adding /P to the command line and attaching the output .i file along with the full command line used to invoke CL.exe. You can also help by verifying that the pre-processed file generates the expected failure. You can do this by invoking your original command line, removing the source file, adding the .i file, and adding /TP (if the original file was C++) or /TC (if the original file was C) to the command line. There is some more information on the /P switch and creating repro cases for the VC++ team here: and here:

I will take a look as soon as you attach the file. The sooner you can do this the better as the window is closing for me to contribute a fix for final release of Visual Studio 11.

ian Bearman
Principal Software Developer
VC++ Code Generation and Optimization
Posted by MS-Moderator10 [Feedback Moderator] on 5/21/2012 at 2:04 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by MS-Moderator01 on 5/18/2012 at 3:43 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(