Global variables of __m128i type behave incorrectly with global optimization. - by Arseny Kapoulkine

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 615374 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 10/20/2010 12:39:16 PM
Access Restriction Public


When using a global variable of __m128i type from several translation units (via extern), the size of the variable differs if global optimizations are enabled.
Sign in to post a comment.
Posted by Shayne [MSFT] on 11/22/2010 at 5:53 PM

This warning is actually a false positive in your case. We plan to fix this issue in the next release of Visual Studio.

If you are currently blocked by this warning, you can add /wd4743 to the command line.
Posted by Microsoft on 10/21/2010 at 2:02 AM
Thank you for reporting the issue.
We are routing 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 Microsoft on 10/20/2010 at 6:35 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(