Open main menu

CDOT Wiki β

Changes

GPU621/Intel Parallel Studio Inspector.

No change in size, 09:07, 9 December 2021
no edit summary
This maximizes the scope of the threading analysis. Using this setting will also maximize the time, resources, and load on the system to perform the analysis. This will detect an extensive range of threading issues including deadlocks and data races. Intel Inspector will display the context of the problem and the highest degree of information available.
 
== Race Conditions ==
 
Intel Inspector can be used to detect race conditions in programs. The following code is an example of race conditions occurring. In it, 5 threads are created to increment the value of an object several times. A race condition occurs when the threads race for the same data, therefore the value will be inconsistent and output different results. Normally in a data race, it becomes hard to locate data manually but with the help of Intel Inspector, it is much faster.
 
 
[[File:RaceConditions.jpg|400px]]
 
[[File:RaceCondition_Output.jpg|500px]]
 
''Values below 20000 are caused by race conditions''
 
Using Intel Inspector we can see where the race condition occurs in the code
 
 
[[File:RaceCondition_Inspector.jpg|800px]]
 
''Indicating where the data race occurs''
== Deadlocks ==
The intel inspector allows us to quickly locate where the error occurs and we can move on to debug the program and find the optimal solution.
 
== Race Conditions ==
 
Intel Inspector can be used to detect race conditions in programs. The following code is an example of race conditions occurring. In it, 5 threads are created to increment the value of an object several times. A race condition occurs when the threads race for the same data, therefore the value will be inconsistent and output different results. Normally in a data race, it becomes hard to locate data manually but with the help of Intel Inspector, it is much faster.
 
 
[[File:RaceConditions.jpg|400px]]
 
[[File:RaceCondition_Output.jpg|500px]]
 
''Values below 20000 are caused by race conditions''
 
Using Intel Inspector we can see where the race condition occurs in the code
 
 
[[File:RaceCondition_Inspector.jpg|800px]]
 
''Indicating where the data race occurs''
= Resources =
61
edits