Hi,
Thanks for providing this flag to enable us to run code coverage using an optimized build. I will definitely have a try.
However by looking at the command-line documentation, I see following descriptions:
-optimized_build
.........
You can see surprising coverage results when the target is compiled with optimization because there can be a big difference between the source code and the generated code.
........
Does that mean the code coverage results could be a little inaccurate due to optimization of the code? I am more keen on the accuracy of code coverage, so if the result is not accurate enough, I would rather run code coverage by removing the build optimization. (use /Od instead of /O1, /O2).
Thanks for providing this flag to enable us to run code coverage using an optimized build. I will definitely have a try.
However by looking at the command-line documentation, I see following descriptions:
-optimized_build
.........
You can see surprising coverage results when the target is compiled with optimization because there can be a big difference between the source code and the generated code.
........
Does that mean the code coverage results could be a little inaccurate due to optimization of the code? I am more keen on the accuracy of code coverage, so if the result is not accurate enough, I would rather run code coverage by removing the build optimization. (use /Od instead of /O1, /O2).





