I am using MDK-ARM V5.37 with arm compile V5 and have noticed that _MSC_VER is defined until I perform a build at which point it becomes undefined.
I have no idea where/why it is defined, it certainly isn't in my code. I don't understand why it is defined and then becomes undefined at the point I perform a build.
It can easily be demonstrated in "main.c" as follows:
#if defined(_MSC_VER) && _MSC_VER >= 1700
int a = 1;
int b = a;
/* Infinite loop */
The Dynamic Syntax Checker is happy with the code and "int a = 1;" is not greyed out, implying _MSC_VER is defined.
Now compile the code and it gives error in main() stating that "a" is undefined.
This only happens when configured for arm compiler V5. When configured for arm compiler V6 "int a = 1;" is greyed out and _MSC_VER is not defined before/during build.
The problem with _MSC_VER being defined as far as DSC is concerned for compiler v5 is as follows:
"platform_util.h" in mbedTLS includes <sal.h> if _MSC_VER is defined. This file does not exist on my PC. Therefore the DSC flags it with a red X and everything thereafter is ignored by the DSC. This results in DSC not working for any file that includes mbedTLS headers. I have raised a support ticket for this.