Help is available by moving the cursor above any symbol or by checking MAQAO website.
[ 4 / 4 ] Application profile is long enough (18.84 s)
To have good quality measurements, it is advised that the application profiling time is greater than 10 seconds.
[ 3 / 3 ] Optimization level option -Ofast is used
To have better performances, it is advised to help the compiler by using a proper optimization level (-Ofast)
[ 3 / 3 ] Helper debug compilation options -g and -fno-omit-frame-pointer are used
-g option gives access to debugging informations, such are source locations and -fno-omit-frame-pointer improve the accuracy of callchains found during the application profiling.
[ 3 / 3 ] Architecture specific option -mcpu is used
[ 2 / 2 ] Application is correctly profiled ("Others" category represents 0 % of the execution time)
To have a representative profiling, it is advised that the category "Others" represents less than 20% of the execution time in order to analyze as much as possible of the user code
[ 4 / 4 ] Enough time of the experiment time spent in analyzed loops (99.97%)
If the time spent in analyzed loops is less than 30%, standard loop optimizations will have a limited impact on application performances.
[ 4 / 4 ] Loop profile is not flat
At least one loop coverage is greater than 4% (45.20%), representing an hotspot for the application
[ 4 / 4 ] Enough time of the experiment time spent in analyzed innermost loops (54.64%)
If the time spent in analyzed innermost loops is less than 15%, standard innermost loop optimizations such as vectorisation will have a limited impact on application performances.
[ 3 / 3 ] Less than 10% (0%) is spend in BLAS1 operations
It could be more efficient to inline by hand BLAS1 operations
[ 3 / 3 ] Cumulative Outermost/In between loops coverage (45.33%) lower than cumulative innermost loop coverage (54.64%)
Having cumulative Outermost/In between loops coverage greater than cumulative innermost loop coverage will make loop optimization more complex
[ 2 / 2 ] Less than 10% (0%) is spend in Libm/SVML (special functions)
[ 2 / 2 ] Less than 10% (0%) is spend in BLAS2 operations
BLAS2 calls usually could make a poor cache usage and could benefit from inlining.
Loop ID | Module | Analysis | Penalty Score | Coverage (%) | Vectorization Ratio (%) | Vector Length Use (%) |
---|---|---|---|---|---|---|
►2372 | exec | Partial or unexisting vectorization - Use pragma to force vectorization and check potential dependencies between array access. | 22 | 45.2 | 0 | 25 |
○ | [SA] Too many paths (16 paths) - Simplify control structure. There are 16 issues ( = paths) costing 1 point each with a malus of 4 points. | 20 | ||||
○ | [SA] Non innermost loop (InBetween) - Collapse loop with innermost ones. This issue costs 2 points. | 2 | ||||
○ | Warning! Some static analysis are missing because the loop has too many paths. Use a higher value for --maximal_path_number option. | 0 | ||||
○2242 | exec | Partial or unexisting vectorization - No issue detected | 0 | 20.33 | 0 | 25 |
○2184 | exec | Partial or unexisting vectorization - No issue detected | 0 | 19.43 | 0 | 25 |
○2495 | exec | Partial or unexisting vectorization - No issue detected | 0 | 12.71 | 0 | 25 |
○2311 | exec | Partial or unexisting vectorization - No issue detected | 0 | 1.06 | 0 | 25 |
○2086 | exec | Partial or unexisting vectorization - No issue detected | 0 | 0.53 | 0 | 0 |
○2097 | exec | Partial or unexisting vectorization - No issue detected | 0 | 0.16 | 0 | 0 |
○2093 | exec | Partial or unexisting vectorization - No issue detected | 0 | 0.11 | 0 | 0 |
○2088 | exec | Partial or unexisting vectorization - No issue detected | 0 | 0.08 | 0 | 0 |
○2108 | exec | Partial or unexisting vectorization - No issue detected | 0 | 0.05 | 0 | 0 |