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.

VivaMP - a tool for OpenMP

VivaMP - a tool for OpenMP

Nov 18 2008

The tool for programmers VivaMP is intended for helping OpenMP-based parallel software developers. The article gives a brief description of the program product.

OpenMP support in PVS-Studio had been dropped after version 5.20. If you have any questions, feel free to contact our support.

OpenMP parallel programming technology: advantages and disadvantages

The modern processor (whether in a desktop or in a laptop) has several cores. Most often there are two cores and more rarely three or four. But very soon even eight cores in a usual desktop computer will be a common thing. That's why the most progressive software developers start thinking right now how to make their programs parallel. That is how to load all the available processor's cores. And although it would be an absolutely correct solution to develop a new parallel version of the program product, it is actually the existing sequential version that is usually "parallelized". There are many different parallel programming technologies but we are interested first of all in OpenMP technology as the most promising for systems with common memory, that is the most promising for paralleling programs intended for desktop computers. It allows you to make the existing program parallel by rewriting its separate sections. All this seems (and actually is) very attractive to developers but here we face a problem. Support of OpenMP technology is implemented in existing developing means so that it is very easy to make errors which are not diagnosed [1]. Because of this developing OpenMP-solutions becomes even more complicated.

A tool for supporting OpenMP-solution developers

To make the process of developing OpenMP-solutions less complicated OOO "Program Verification Systems" creating program products in the sphere of code analysis has developed the program product VivaMP.

VivaMP is a C/C++ code analyzer intended for searching errors in existing OpenMP-programs and for simplifying the process of developing new OpenMP-programs. If there are errors in a parallel program which cannot be diagnosed by the compiler VivaMP will find them. After that the developer can easily correct these errors using the Help system embedded into VivaMP.

Technically, VivaMP tool is implemented as an add-in module (AddIn) for Visual Studio 2005/2008 (figure 1).


Figure 1 - VivaMP tool is embedded into Microsoft Visual Studio 2005/2008 environment

After testing a separate file, project or whole solution the analyzer prints the list of potential errors the developer should look through into Error List. You can get information on each error in the Help system integrating into MSDN.

VivaMP tool allows you to:

  • find old errors in existing OpenMP-solutions;
  • detect errors in new OpenMP-solutions being developed;
  • get information on correcting errors in the Help system;
  • increase performance of OpenMP-based solutions;
  • investigate most of the possible errors in OpenMP-solutions using both the documentation and the demo-program ParallelSample attached to the VivaMP distribution kit.

The stated ways of using VivaMP make this tool useful both for first-time OpenMP-programmers and their more experienced colleagues.

Advantages of static analysis over other methods of searching parallel errors

VivaMP tool is a static code analyzer. This means that unlike dynamic analyzers it doesn't require launching the program being tested to detect errors, and the result of the static analyzer's work doesn't depend on the execution environment. Static analysis allows you to test the code which receives control rarely or which is executed when processing rare errors.

Verification of parallel programs with the help of static analysis method is considered to be difficult and ineffective as it is impossible to detect errors occurring when different program parts interact. But in case of OpenMP technology you can effectively use static analysis. It is because of OpenMP technology's "local" character. As a rule, parallel code in programs is gathered in one place and this helps perform detailed static analysis for detecting errors. To learn more about this subject see the article "Testing parallel programs" [2].


If you develop parallel programs using OpenMP technology you need to get acquainted with VivaMP tool. It will help you make development of OpenMP-solutions much simpler and quicker.


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…
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…
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…
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…
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…
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 Evil within the Comparison Functions

Date: May 19 2017

Author: Andrey Karpov

Perhaps, readers remember my article titled "Last line effect". It describes a pattern I've once noticed: in most cases programmers make an error in the last line of similar text blocks. Now I want t…

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 →