This article describes a problem that occurs when you use a C++ compiler to compile deeply nested templates that have been inlined on a Windows Embedded Compact 2013-based device. In this situation, the compiler optimizer crashes because of invalid internal compiler data structures.Â
Additionally, you receive the following error message:
fatal error C1001: An internal error has occurred in the compiler.
An update is available to resolve this problem. The update requires that all previously issued updates for this product are also installed.
More Information
Software update information
Download information
Windows Embedded Compact 2013 Monthly Update (March 2015) is now available from Microsoft. To download this Windows Embedded Compact 2013 monthly update, go to Microsoft OEM Online or MyOEM.
Restart requirement
After you apply this update, you must perform a clean build of the whole platform. To do this, use one of the following methods:
-
On the Build menu, click Clean Solution, and then click Build Solution.
-
On the Build menu, click Rebuild Solution.
You do not have to restart the computer after you apply this software update.
Update replacement information
This update does not replace any other updates.
The English version of this software update package has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Files that are included in this hotfix package
|
File name |
File size |
Date |
Time |
Path |
|---|---|---|---|---|
|
Armasm.exe |
235,592 |
20-Aug-2014 |
17:21 |
Public\Common\Sdk\Bin\I386\Arm |
|
C1.dll |
709,224 |
19-Mar-2015 |
15:47 |
Public\Common\Sdk\Bin\I386\Arm |
|
C1ast.dll |
872,520 |
20-Aug-2014 |
17:21 |
Public\Common\Sdk\Bin\I386\Arm |
|
C1xx.dll |
2,812,528 |
19-Mar-2015 |
15:47 |
Public\Common\Sdk\Bin\I386\Arm |
|
C1xxast.dll |
3,053,136 |
20-Aug-2014 |
17:21 |
Public\Common\Sdk\Bin\I386\Arm |
|
C2.dll |
3,535,976 |
19-Mar-2015 |
15:47 |
Public\Common\Sdk\Bin\I386\Arm |
|
Cl.exe |
148,584 |
19-Mar-2015 |
15:47 |
Public\Common\Sdk\Bin\I386\Arm |
|
Link.exe |
829,040 |
19-Mar-2015 |
15:47 |
Public\Common\Sdk\Bin\I386\Arm |
|
Mspdb110.dll |
256,592 |
19-Mar-2015 |
15:47 |
Public\Common\Sdk\Bin\I386\Arm |
|
Clui.dll |
462,960 |
19-Mar-2015 |
15:47 |
Public\Common\Sdk\Bin\I386\Arm\1033 |
|
Linkui.dll |
78,408 |
20-Aug-2014 |
17:21 |
Public\Common\Sdk\Bin\I386\Arm\1033 |
|
Armasm.exe |
235,640 |
20-Aug-2014 |
17:23 |
Sdk\Bin\I386\Arm |
|
C1.dll |
709,224 |
20-Aug-2014 |
17:23 |
Sdk\Bin\I386\Arm |
|
C1ast.dll |
872,568 |
20-Aug-2014 |
17:23 |
Sdk\Bin\I386\Arm |
|
C1xx.dll |
2,812,528 |
20-Aug-2014 |
17:24 |
Sdk\Bin\I386\Arm |
|
C1xxast.dll |
3,053,176 |
20-Aug-2014 |
17:24 |
Sdk\Bin\I386\Arm |
|
C2.dll |
3,535,976 |
20-Aug-2014 |
17:24 |
Sdk\Bin\I386\Arm |
|
Cl.exe |
148,584 |
20-Aug-2014 |
17:24 |
Sdk\Bin\I386\Arm |
|
Link.exe |
829,040 |
20-Aug-2014 |
17:24 |
Sdk\Bin\I386\Arm |
|
Msvcp110.dll |
535,680 |
20-Aug-2014 |
17:24 |
Sdk\Bin\I386\Arm |
|
Msvcp110d.dll |
821,896 |
20-Aug-2014 |
17:24 |
Sdk\Bin\I386\Arm |
|
Msvcr110.dll |
874,624 |
20-Aug-2014 |
17:24 |
Sdk\Bin\I386\Arm |
|
Msvcr110d.dll |
1,701,000 |
20-Aug-2014 |
17:24 |
Sdk\Bin\I386\Arm |
|
Clui.dll |
462,960 |
20-Aug-2014 |
17:23 |
Sdk\Bin\I386\Arm\1033 |
|
Linkui.dll |
78,456 |
20-Aug-2014 |
17:23 |
Sdk\Bin\I386\Arm\1033 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
For more information about software update terminology, see Description of the standard terminology that is used to describe Microsoft software updates.
