Originally, -fstrict-aliasing and -fno-strict-aliasing were gcc specific optimization flags (see https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#index-fstrict-aliasing). But of course, other compilers that are meant as drop-in replacements for gcc, such as Intel's icc and LLVM's clang, support this flag to, with the same meaning.

However, there are definitely compilers out there which will not support this flag, for example the Microsoft C/C++ compiler. Does this commit affect the flags passed to Microsoft C/C++?