[thedoctor79]

I'm sorry, but the quality of comments on that question is really low, apart from one. A malicious compiler can easily insert malicious code into you executable, and if you are not able to trust your compiler or read the code it generates, then you would be better off relying on the antivirus. Then again, with the prevailing mentality of most Windows users of installing packages from untrusted sources and running unknown binaries without understanding the risks, it is not surprising.

[userbinator]

How many malicious compilers have you actually seen in the wild (in 2012, when that post was written)? And indeed if there were any, why would an AV not just detect the compiler itself?

[OJFord]

> why would an AV not just detect the compiler itself?

Because then users of a binary need to trust that the compiler-user had an AV installed.