Article ID: 195376 - View products that this article applies to.
This article was previously published under Q195376
This article has been archived. It is offered "as is" and will no longer be updated.
The compiler might generate incorrect code when building with /Og (Global Optimizations) and /Oa (Assume No Aliasing) or /Og and /Ow (Assume Cross-function Aliasing).
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This bug was corrected in Visual Studio 6.0 Service Pack 3. For more information about Visual Studio service packs, please see the following articles in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/194022/EN-US/ )INFO: Visual Studio 6.0 Service Packs, What, Where, Why
(https://support.microsoft.com/kb/194295/EN-US/ )HOWTO: Tell That Visual Studio 6.0 Service Packs Are Installed
Please refer to Help for more information about the compiler options /Og, /Oa, and /Ow.
The following sample demonstrates the bug. In this case, the problem appears to be related to the final attempt to access an array in a function when that access involves doubling the variable used to index it.
The program output should be: 3.0.
The program output is: 2.000000.
Article ID: 195376 - Last Review: January 6, 2015 - Revision: 1.1