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.
The Intel Advisor provides an annotation assistant near the bottom of the Survey Report and Survey Source windows, as well as with the No Data message. Use this assistant to copy selected annotated code snippets and build setting information into a code editor. For example, here is the annotation assistant pane in the Survey Report window:
After running the Intel Advisor tools to analyze your running application's target, the displayed report may contain information about your target's debug (symbol) information that is unexpected or does not make sense. When debug information is not available, the ability to use binary-to-source correlation prevents the display of source code. For example:
This row shows a source location where memory is being freed using a non-standard or user-defined memory deallocation. The Dependencies tool uses this as a hint about the lifetime of memory accesses, so memory that is freed and then allocated again will not cause conflicts to be reported if the non-standard or user-defined memory free occurs with the span of this annotation's execution.
Occurs when a parallel site was executed but annotations for only one task instance were executed in the dynamic extent of the active parallel site. This may be the expected behavior, or it may indicate an error in the placement of annotations or a data set that is not well suited for parallelism.
Use this pane to select which source code appears in the Focus Code Location pane. The top of the Call Stack initially displays the focus code location ( icon). The current row is for a loop in the call stack .
To access this dialog box:
From the Intel Advisor GUI, choose Project > Project Properties (or equivalent). In the Project Properties dialog box, click the Binary/Symbol Search tab.