PVS-Studio 3.30 release took place on September 25, 2009


The main feature of this code analyzer version, PVS-Studio, is the possibility of testing 32-bit projects for estimating the complexity and cost of code migration to 64-bit systems. Due to this possibility, it is possible to estimate yet before the start of code migration procedure to what extent this process will be labor intensive.

Among other improvements, there are: addition of new rules of potential errors diagnostics, correct work with installed Intel C++ Compiler, as well as extension of support of localized Visual Studio versions.

Here is the full list of innovations:

  • In PVS-Studio, the possibility of testing 32-bit projects for estimating the complexity and cost of code migration to 64-bit systems has been added.
  • A new rule for 64-bit code analysis has been added, V118: malloc() function accepts a dangerous expression in the capacity of an argument.
  • A new rule for 64-bit code analysis has been added, V119: More than one sizeof() operators are used in one expression.
  • A new rule for parallel code analysis has been added, V1211: The use of 'flush' directive has no sense for private '%1%' variable, and can reduce performance.
  • Combined operation with Intel C++ Compiler has been improved (crash at the attempt of code verification with installed Intel C++ Compiler has been corrected.)
  • Localized versions of Visual Studio support has been enhanced.


Use PVS-Studio to search for bugs in C, C++, C# and Java

We offer you to check your project code with PVS-Studio. Just one bug found in the project will show you the benefits of the static code analysis methodology better than a dozen of the articles.

goto PVS-Studio;



Bugs Found

Checked Projects
336
Collected Errors
12 743