options

exec - 2023-10-24 22:20:38 - MAQAO 2.17.9

Help is available by moving the cursor above any symbol or by checking MAQAO website.

Stylizer  

[ 4 / 4 ] Application profile is long enough (57.61 s)

To have good quality measurements, it is advised that the application profiling time is greater than 10 seconds.

[ 0 / 3 ] Optimization level option not used

To have better performances, it is advised to help the compiler by using a proper optimization level (-O2 of higher). Warning, depending on compilers, faster optimization levels can decrease numeric accuracy.

[ 0 / 3 ] Helper debug compilation options -g and -fno-omit-frame-pointer are missing

-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.

[ 0 / 3 ] Architecture specific options are not used [AARCH64]

Architecture specific options are needed to produce efficient code for a specific processor ( -mcpu=native ).

[ 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

Strategizer  

[ 4 / 4 ] Enough time of the experiment time spent in analyzed loops (99.96%)

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% (89.01%), representing an hotspot for the application

[ 0 / 4 ] Too little time of the experiment time spent in analyzed innermost loops (10.95%)

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

[ 0 / 3 ] Cumulative Outermost/In between loops coverage (89.01%) greater than cumulative innermost loop coverage (10.95%)

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.

Optimizer

Loop IDModuleAnalysisPenalty ScoreCoverage (%)Vectorization
Ratio (%)
Vector Length
Use (%)
12execPartial or unexisting vectorization - Use pragma to force vectorization and check potential dependencies between array access.289.0174.0791.36
[SA] Non innermost loop (Outermost) - Collapse loop with innermost ones. This issue costs 2 points.2
10execPartial or unexisting vectorization - No issue detected06.36018.75
11execPartial or unexisting vectorization - No issue detected04.45018.75
9execPartial or unexisting vectorization - Use pragma to force vectorization and check potential dependencies between array access.10000.09016.67
[SA] Too many paths (at least 1000 paths) - Simplify control structure. There are at least 1000 issues ( = paths) costing 1 point.1000
Warning! Some static analysis are missing because the loop has too many paths. Use a higher value for --maximal_path_number option.0
8execPartial or unexisting vectorization - Use pragma to force vectorization and check potential dependencies between array access.10.03017.79
[SA] Presence of calls - Inline either by compiler or by hand and use SVML for libm calls. There are 1 issues (= calls) costing 1 point each.1
5execPartial or unexisting vectorization - No issue detected00.0192.86100
Warning! There is no dynamic data for this loop. Some checks can not been performed.0
2execThe loop is fully and efficiently vectorized.00.01100100
Warning! There is no dynamic data for this loop. Some checks can not been performed.0
×