Link /LTCG:PGI internal error (target xp) - by s793016s

Status : 

  Duplicate<br /><br />
		This item appears to be a duplicate of another existing Connect or internal item.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 776382 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 1/11/2013 4:47:25 PM
Access Restriction Public

Description

Sorry, my English is very very poor.

I tried to build Mozilla Firefox 17.0.1 with VS2012 target xp.

In the PGI phase get this error:
=======================
d:/mozilla/mozilla/config/pythonpath.py -I../../config d:/mozilla/mozilla/config/expandlibs_exec.py --depend .deps/xul.dll.pp --target xul.dll --uselist -- link -NOLOGO -DLL -OUT:xul.dll -PDB:xul.pdb -SUBSYSTEM:WINDOWS -MACHINE:X86  dlldeps   Creating library xul.lib and object xul.exp
Generating code
Finished generating code
PGOCVT : fatal error PG0001: An unexpected internal error was detected in source file 'f:\dd\vctools\compiler\utc\src\tools\pogo\cvtpgd\cvtpgd.cpp', line 681.
PGOCVT : fatal error PG0001: An unexpected internal error was detected in source file 'f:\dd\vctools\compiler\utc\src\tools\pogo\cvtpgd\cvtpgd.cpp', line 712.
=====================================
after this message the compiler will continue to the end, and the binary will crash because xul.dll crash.

ac_add_options --enable-optimize="-O2 -GL -arch:IA32" 
Sign in to post a comment.
Posted by Pratap [MSFT] on 1/25/2013 at 5:50 PM
Thank you for reporting this issue. The issue involved the high number of indirect call targets (function pointers, virtual functions, etc) in the binary. This issue has been fixed and will be available in a future release.
Posted by Macy [MSFT] on 1/13/2013 at 11:04 PM
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 Macy [MSFT] on 1/11/2013 at 4:51 PM
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)