Pour obtenir une clé
d'essai remplissez le formulaire ci-dessous
Demandez des tariffs
Nouvelle licence
Renouvellement de licence
--Sélectionnez la devise--
* En cliquant sur ce bouton, vous acceptez notre politique de confidentialité

Free PVS-Studio license for Microsoft MVP specialists
To get the licence for your open-source project, please fill out this form
** En cliquant sur ce bouton, vous acceptez notre politique de confidentialité.

I am interested to try it on the platforms:
** En cliquant sur ce bouton, vous acceptez notre politique de confidentialité.

Votre message a été envoyé.

Nous vous répondrons à

Si vous n'avez toujours pas reçu de réponse, vérifiez votre dossier
Spam/Junk et cliquez sur le bouton "Not Spam".
De cette façon, vous ne manquerez la réponse de notre équipe.

Does the result of static code analysis…

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

17 Déc 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.

Comments (0)

Next comments
Unicorn with delicious cookie
Nous utilisons des cookies pour améliorer votre expérience de navigation. En savoir plus