When viewing the Annotation Report window, if you see unmatched annotations in the Annotation Report window, the cause may be that multiple annotations were placed on a single statement line or the code used annotations located inside macros. For example, some annotations may appear to be unmatched or not appear in the Annotation Report window.
The Annotation Report window lists the Intel Advisor XE annotations found in the sources for the project and annotations data related to the Intel Advisor XE tools.
After you run the Suitability or Dependencies tools, the Annotation Report window may show unexpected unmatched annotations.
Possible causes include:
Placing multiple annotations in a single statement line. Instead, place each annotation on a separate statement line.
Placing annotations inside preprocessor macros for C/C++ code.
These Intel Advisor XE limitations are similar to debugger breakpoint limitations.
After you run the Suitability or Dependencies tools, if the Annotation Report window shows:
One or more unexpected Unmatched annotation(s) that refer to the same source line under the Source column. View the source code to determine whether multiple annotations were placed on a single statement line. Annotations must be placed on a single statement line so Intel Advisor XE tools have sufficient information to disambiguate annotations for data collection.
One or more unexpected Unmatched annotation(s) and the Source column refers to the source line where the preprocessor macro is defined - and not the actual desired code location. View the C/C++ source code to determine whether this is caused by placing annotations in preprocessor macros. This occurs because there is no source correlation from entities appearing inside macros to the actual source location that is used for data collection.
Do the following:
Use the Annotation Report window to view the code region(s) causing the problem. If you suspect that the problem is caused by multiple annotations placed on a single statement line, modify the source code so each annotation appears on a separate line. Rebuild your target, run the Suitability or Dependencies tool, and view the Annotation Report window again.
Use the
Annotation Report window to view the C/C++ code region(s) causing the problem (click the
icon). If you suspect the problem is caused by inserting annotations inside macros, modify the C/C++ source code to remove the annotations from the macros and add them to the location(s) in the sources where the macros currently appear. Rebuild your target, run the Suitability or Dependencies tool, and view the
Annotation Report window again.