To get a trial key
fill out the form below
Team License (a basic version)
Enterprise License (an extended version)
* By clicking this button you agree to our Privacy Policy statement

Request our prices
New License
License Renewal
--Select currency--
* By clicking this button you agree to our Privacy Policy statement

Free PVS-Studio license for Microsoft MVP specialists
* By clicking this button you agree to our Privacy Policy statement

To get the licence for your open-source project, please fill out this form
* By clicking this button you agree to our Privacy Policy statement

I am interested to try it on the platforms:
* By clicking this button you agree to our Privacy Policy statement

Message submitted.

Your message has been sent. We will email you at

If you haven't received our response, please do the following:
check your Spam/Junk folder and click the "Not Spam" button for our message.
This way, you won't miss messages from our team in the future.

Does the result of static code analysis…

Does the result of static code analysis depend on the compiler being used?

Dec 17 2009

At one of the many discussions of static code analyzers, we mentioned our tool PVS-Studio as usual :-) . One of the participants asked: "Does the result of a static code analyzer depend on the compiler being used at all?" The answer to this question is much more complicated than it seemed at first. That is why you see this post.

Visual Studio 2005 and 2008 development environments are no longer supported. You can view the list of supported development environments in the documentation section "System requirements for PVS-Studio analyzer".

A brief version of the answer is as follows. The static code analyzer is a tool that does not depend on the compiler at all and uses its own techniques to parse the code and search for issues in it. But this is in theory and what do we have in practice?

First, static code analyzer developers very often prefer some development tools they are used to and leave aside (of course unfairly) some others. For example, if a tool is designed for a Windows-platform, it will most likely fail to work with GCC. And even concerning the Windows-platform, a tool intended for Microsoft products will scarcely work efficiently with Embarcadero (Borland followers) products. For if we speak, for example, of C++ language, developers of different compilers always have some mutually incompatible features. It might be explained by the C++ standard size or by the intrigues of marketing wars. One way or another, the fact remains.

Second, the static code analyzer might well use the compiler, at least partly. For example, our PVS-Studio analyzer uses the external preprocessor. And of course it impacts its operation.

Third, even using the same development tool (compiler) but of different versions together with the static analyzer might also have some influence. For example, we have tests for PVS-Studio - about 30 applications (90 projects) in the form of the source codes. Full testing of this set with our tool takes an hour and a half in Visual Studio 2005 and two hours in Visual Studio 2008. The difference is 1.4 times! Where does it come from? You can easily find the answer if you just preprocess all the files being tested and watch the result size. Now it is 1278 files. The size of the preprocessed files in Visual Studio 2005 is 4850 Mbytes and in Visual Studio 2008 - 6850 Mbytes. The difference is these very 1.4 times. I.e. the user code being absolutely the same, the difference between the header files determines the difference between the final codes processed by the analyzer of 1.4 times.

So, it turns out that the compiler you use influences very much what the code analyzer tests.

Popular related articles
PVS-Studio ROI

Date: Jan 30 2019

Author: Andrey Karpov

Occasionally, we're asked a question, what monetary value the company will receive from using PVS-Studio. We decided to draw up a response in the form of an article and provide tables, which will sho…
How PVS-Studio Proved to Be More Attentive Than Three and a Half Programmers

Date: Oct 22 2018

Author: Andrey Karpov

Just like other static analyzers, PVS-Studio often produces false positives. What you are about to read is a short story where I'll tell you how PVS-Studio proved, just one more time, to be more atte…
Appreciate Static Code Analysis!

Date: Oct 16 2017

Author: Andrey Karpov

I am really astonished by the capabilities of static code analysis even though I am one of the developers of PVS-Studio analyzer myself. The tool surprised me the other day as it turned out to be sma…
Static analysis as part of the development process in Unreal Engine

Date: Jun 27 2017

Author: Andrey Karpov

Unreal Engine continues to develop as new code is added and previously written code is changed. What is the inevitable consequence of ongoing development in a project? The emergence of new bugs in th…
The Last Line Effect

Date: May 31 2014

Author: Andrey Karpov

I have studied many errors caused by the use of the Copy-Paste method, and can assure you that programmers most often tend to make mistakes in the last fragment of a homogeneous code block. I have ne…
PVS-Studio for Java

Date: Jan 17 2019

Author: Andrey Karpov

In the seventh version of the PVS-Studio static analyzer, we added support of the Java language. It's time for a brief story of how we've started making support of the Java language, how far we've co…
The Ultimate Question of Programming, Refactoring, and Everything

Date: Apr 14 2016

Author: Andrey Karpov

Yes, you've guessed correctly - the answer is "42". In this article you will find 42 recommendations about coding in C++ that can help a programmer avoid a lot of errors, save time and effort. The au…
Characteristics of PVS-Studio Analyzer by the Example of EFL Core Libraries, 10-15% of False Positives

Date: Jul 31 2017

Author: Andrey Karpov

After I wrote quite a big article about the analysis of the Tizen OS code, I received a large number of questions concerning the percentage of false positives and the density of errors (how many erro…
Technologies used in the PVS-Studio code analyzer for finding bugs and potential vulnerabilities

Date: Nov 21 2018

Author: Andrey Karpov

A brief description of technologies used in the PVS-Studio tool, which let us effectively detect a large number of error patterns and potential vulnerabilities. The article describes the implementati…
Free PVS-Studio for those who develops open source projects

Date: Dec 22 2018

Author: Andrey Karpov

On the New 2019 year's eve, a PVS-Studio team decided to make a nice gift for all contributors of open-source projects hosted on GitHub, GitLab or Bitbucket. They are given free usage of PVS-Studio s…

Comments (0)

Next comments
This website uses cookies and other technology to provide you a more personalized experience. By continuing the view of our web-pages you accept the terms of using these files. If you don't want your personal data to be processed, please, leave this site.
Learn More →