Useless C++ C4700 warning for x64 Release builds - by CoolCmd

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 591804 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 8/31/2010 3:21:46 AM
Access Restriction Public


64-bit C++ compiler generate C4700 warning for valid code. 32-bit compiler do not have this bug.
Sign in to post a comment.
Posted by Microsoft on 12/16/2010 at 3:57 PM
Hello, CoolCmd.

We had fixed the issue and should be available on next version. At this time, I can only recommend spliting the function call and the condition into two lines. The compiler will still produce similar code without the warning.


Felix Huang
Posted by CoolCmd on 10/8/2010 at 4:15 AM
Felix Huang, I don't have issues with linker. Its compiler's warning.
Posted by Microsoft on 10/1/2010 at 3:15 PM
Hello CoolCmdMS,
We still looking into the issue. What we found is that link incremental isn't regenerating the executable when the obj changed. If you disable incremental linking, then the executable would be created. To disable incremental linking, set "No" in property pages Linker->General->"Enable Incremental Linking".


Felix Huang
Posted by Microsoft on 8/31/2010 at 6:53 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 Microsoft on 8/31/2010 at 5:01 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(