Unexpected Unmatched Annotations in the Dependencies Report
- You placed annotations inside macros.
- For Linux* OS: You placed parallel sites and their related annotations outside the project.
- For Windows* OS: You placed parallel sites and their related annotations outside a set of projects that the startup project depends on.
- Your sources contain huge source files that contain annotations. As only the first 8 MB of each file are parsed for annotations (for performance reasons), this could possibly cause mismatched annotations messages.
- Use the Dependencies tool to view the code region(s) causing the problem. Investigate whether some sites or tasks may have multiple exit points and whether end annotations cover all exit points. For example, code that returns or branches around an end annotation, or throws an exception. If you suspect the problem is caused by adding annotations inside macros, remove the annotations from the macros and add them to the final location in the sources - similar to the way breakpoints do not work in macros. Rebuild your target and run the Dependencies tool again.
- Windows* OS only: Use the Dependencies tool to investigate by viewing the code region(s) causing the problem.If you suspect that parallel sites and their related annotations that are placed outside the set of projects that the startup project depends on, consider using the Visual Studio* Project Dependencies context menu item to add appropriate dependencies to causeRebuild and run the Dependencies tool again.Intel Advisorto scan sources in the additional project(s).
- If your sources include huge source files that contain annotations (more than 8 MB per file) , consider breaking each huge source file into several source files.