Help is available by moving the cursor above any 
symbol or by checking MAQAO website.
[ 4 / 4 ] Application profile is long enough (146.93 s)
To have good quality measurements, it is advised that the application profiling time is greater than 10 seconds.
[ 3.00 / 3 ] Optimization level option is correctly used
[ 2.99 / 3 ] Most of time spent in analyzed modules comes from functions compiled with -g and -fno-omit-frame-pointer
-g option gives access to debugging informations, such are source locations. -fno-omit-frame-pointer improve the accuracy of callchains found during the application profiling.
[ 2.99 / 3 ] Architecture specific option -mcpu is used
[ 2 / 2 ] Application is correctly profiled ("Others" category represents 0.02 % 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 (55.24%)
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% (24.57%), representing an hotspot for the application
[ 4 / 4 ] Enough time of the experiment time spent in analyzed innermost loops (54.94%)
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.00%) is spend in BLAS1 operations
It could be more efficient to inline by hand BLAS1 operations
[ 3 / 3 ] Cumulative Outermost/In between loops coverage (0.31%) lower than cumulative innermost loop coverage (54.94%)
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.01%) is spend in Libm/SVML (special functions)
[ 2 / 2 ] Less than 10% (0.01%) is spend in BLAS2 operations
BLAS2 calls usually could make a poor cache usage and could benefit from inlining.
| Loop ID | Analysis | Penalty Score |
|---|---|---|
| ○Loop 1114 - miniqmc | Execution Time: 24 % - Vectorization Ratio: 100.00 % - Vector Length Use: 100.00 % | |
| ○Loop 1082 - miniqmc | Execution Time: 10 % - Vectorization Ratio: 0.00 % - Vector Length Use: 25.00 % | |
| ►Loop 3004 - miniqmc | Execution Time: 8 % - Vectorization Ratio: 0.00 % - Vector Length Use: 25.00 % | |
| ►Loop Computation Issues | 2 | |
| ○ | [SA] Presence of a large number of scalar integer instructions - Simplify loop structure, perform loop splitting or perform unroll and jam. This issue costs 2 points. | 2 |
| ►Loop 3824 - miniqmc | Execution Time: 5 % - Vectorization Ratio: 0.00 % - Vector Length Use: 25.00 % | |
| ►Loop Computation Issues | 6 | |
| ► | [SA] Presence of expensive FP instructions - Perform hoisting, change algorithm, use SVML or proper numerical library or perform value profiling (count the number of distinct input values). There are 1 issues (= instructions) costing 4 points each. | 4 |
| ○ | Number of SQRT instructions: 1 | |
| ○ | [SA] Presence of a large number of scalar integer instructions - Simplify loop structure, perform loop splitting or perform unroll and jam. This issue costs 2 points. | 2 |
| ►Loop 501 - miniqmc | Execution Time: 1 % - Vectorization Ratio: 0.00 % - Vector Length Use: 18.95 % | |
| ►Loop Computation Issues | 2 | |
| ○ | [SA] Presence of a large number of scalar integer instructions - Simplify loop structure, perform loop splitting or perform unroll and jam. This issue costs 2 points. | 2 |
| ►Control Flow Issues | 1000 | |
| ○ | [SA] Too many paths (6561 paths) - Simplify control structure. There are 6561 issues ( = paths) costing 1 point, limited to 1000. | 1000 |
| ►Vectorization Roadblocks | 1000 | |
| ○ | [SA] Too many paths (6561 paths) - Simplify control structure. There are 6561 issues ( = paths) costing 1 point, limited to 1000. | 1000 |
| ○Loop 809 - miniqmc | Execution Time: 0 % - Vectorization Ratio: 100.00 % - Vector Length Use: 100.00 % | |
| ►Loop 3164 - miniqmc | Execution Time: 0 % - Vectorization Ratio: 65.57 % - Vector Length Use: 77.87 % | |
| ►Loop Computation Issues | 16 | |
| ► | [SA] Presence of expensive FP instructions - Perform hoisting, change algorithm, use SVML or proper numerical library or perform value profiling (count the number of distinct input values). There are 4 issues (= instructions) costing 4 points each. | 16 |
| ○ | Number of SQRT instructions: 4 | |
| ►Loop 3165 - miniqmc | Execution Time: 0 % - Vectorization Ratio: 65.57 % - Vector Length Use: 77.87 % | |
| ►Loop Computation Issues | 16 | |
| ► | [SA] Presence of expensive FP instructions - Perform hoisting, change algorithm, use SVML or proper numerical library or perform value profiling (count the number of distinct input values). There are 4 issues (= instructions) costing 4 points each. | 16 |
| ○ | Number of SQRT instructions: 4 | |
| ►Loop 1078 - miniqmc | Execution Time: 0 % - Vectorization Ratio: 0.00 % - Vector Length Use: 25.00 % | |
| ►Loop Computation Issues | 4 | |
| ○ | [SA] Less than 10% of the FP ADD/SUB/MUL arithmetic operations are performed using FMA - Reorganize arithmetic expressions to exhibit potential for FMA. This issue costs 4 points. | 4 |
| ○Loop 1286 - miniqmc | Execution Time: 0 % - Vectorization Ratio: 80.00 % - Vector Length Use: 85.00 % |