After you add Intel Cilk Plus synchronization code (such as reducers/mutexes), but before adding the constructs that cause the program to use parallel execution, you should test your serial program. The synchronization code may introduce problems if you have inadvertently used a non-recursive mutex in a recursive context, or if your edits accidentally changed some other piece of program behavior.
After you add parallel framework code to your program, use the related Intel software products to check for parallel thread errors and improve the performance of your parallel program. Tips for debugging parallel code are also provided.
You can add Intel Advisor annotations in your source code by:
A message appears when you start the Intel Advisor Dependencies tool and the current build options selected is a Release build.
For the Dependencies tool, use a Debug build of your program, not a Release build.
Use this special-purpose annotation to report the access operations to a memory location in the Dependencies Report. This information can help you understand what code accesses a memory location. When you have learned enough, remove the annotation from your source code.
To access the Dependencies Report tab in the Result tab, click the Refinement Reports tab, or run the Dependencies tool. If the Dependencies tool did not detect any Problems, a No Problems Detected message appears instead.
Occurs when an end task annotation is executed but there is no active task.
To access this dialog box:
In the Intel Advisor GUI, choose File > Options... and choose the Result Location page.
Use this dialog box to specify the directory to contain future Intel Advisor results.