Dependencies and Memory Access Patterns Analyses
Refinement Reports Purpose and Usage
- Dependencies analysis (optional) -For safety purposes, the compiler is often conservative when assuming data dependencies. Run a Dependencies analysis to check for real data dependencies in loops the compiler did not vectorize because of assumed dependencies. If real dependencies are detected, the analysis can provide additional details to help resolve the dependencies. Your objective: Identify and better characterize real data dependencies that could make forced vectorization unsafe.
- Memory Access Patterns (MAP) analysis (optional) -Run a MAP analysis to check for various memory issues, such as non-contiguous memory accesses and unit stride vs. non-unit stride accesses. Your objective: Eliminate issues that could lead to significant vector code execution slowdown or block automatic vectorization by the compiler.
Refinement Reports Regions
- Advanced View pane - includes the following tabs:
- Recommendations tab - provides memory-specific recommendations.