Linker internal error/crash for x64 OpenMP - by Sierwald Software GmbH

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 668324 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 5/13/2011 2:28:38 AM
Access Restriction Public


I use the 
#pragma omp parallel for
for a loop and it makes the linker crash on x64. Linking for x32 works fine.

Sample project attached, in C, 84 lines of code.
Sign in to post a comment.
Posted by Microsoft on 6/24/2011 at 12:44 PM
Thanks for reporting this issue. I've verified that the compiler is incorrectly accessing a null pointer during comiplation of your test case. This issue will be fixed in a future release of Visual Studio.

You can work around this bug be disabling optimizations in the function that fails to compile or possibly by modifying your source slightly. The issue is related to the implicit converts in your loop between 32-bit integers and 64-bit pointers, so changing some of the loop variables to be 64-bits wide when targeting x64 may be a good work around for you. I was able to make the sample compile by changing "cycle" from type long (32-bits) to type "long long" (64-bits).

ian Bearman
VC++ Code Generation and Optimization Team

Posted by MS-Moderator10 [Feedback Moderator] on 5/15/2011 at 9:18 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-Moderator10 on 5/15/2011 at 6:34 PM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly (