options

AVBP_V7.16.0.KRAKEN - 2025-05-12 10:20:44 - MAQAO 2.21.4

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

  • run_0

Stylizer  

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

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

[ 1.72 / 3 ] Most of time spent in analyzed modules comes from functions without compilation information

Functions without compilation information (typically not compiled with -g) cumulate 28.36% of the time spent in analyzed modules. Check that -g is present. Remark: if -g is indeed used, this can also be due to some compiler built-in functions (typically math) or statically linked libraries. This warning can be ignored in that case.

[ 2.66 / 3 ] Optimization level option is correctly used

[ 3 / 3 ] Host configuration allows retrieval of all necessary metrics.

[ 0 / 3 ] Compilation of some functions is not optimized for the target processor

Application run on the SKYLAKE micro-architecture while the code was specialized for CORE-AVX2. Architecture specific options are needed to produce efficient code for a specific processor ( -x(target) or -ax(target) ).

[ 2 / 2 ] Application is correctly profiled ("Others" category represents 8.84 % 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

[ 1 / 1 ] Lstopo present. The Topology lstopo report will be generated.

Strategizer  

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

If the time spent in analyzed loops is less than 30%, standard loop optimizations will have a limited impact on application performances.

[ 4 / 4 ] CPU activity is good

CPU cores are active 99.58% of time

[ 4 / 4 ] Threads activity is good

On average, more than 99.48% of observed threads are actually active

[ 4 / 4 ] Affinity is good (100.00%)

Threads are not migrating to CPU cores: probably successfully pinned

[ 0 / 4 ] Loop profile is flat

No hotspot found in the application (greatest loop coverage is 0.98%), and the twenty hottest loops cumulated coverage is lower than 20% of the application profiled time (7.59%)

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

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 ] Cumulative Outermost/In between loops coverage (6.02%) lower than cumulative innermost loop coverage (9.72%)

Having cumulative Outermost/In between loops coverage greater than cumulative innermost loop coverage will make loop optimization more complex

[ 3 / 3 ] Less than 10% (0.00%) is spend in BLAS1 operations

It could be more efficient to inline by hand BLAS1 operations

[ 2 / 2 ] Less than 10% (0.00%) is spend in BLAS2 operations

BLAS2 calls usually could make a poor cache usage and could benefit from inlining.

[ 2 / 2 ] Less than 10% (0.00%) is spend in Libm/SVML (special functions)

Optimizer

Loop IDAnalysisPenalty Score
Loop 15254 - AVBP_V7.16.0.KRAKEN+Execution Time: 0 % - Vectorization Ratio: 0.00 % - Vector Length Use: 6.25 %
Loop Computation Issues+5
[DA] Low iteration count (8.21 < 10) - Perform full unroll. Use compiler pragmas. Use PGO/FDO compiler options. Force compiler to use masked instructions. This issue costs 5 points.5
Control Flow Issues+9
[SA] Several paths (4 paths) - Simplify control structure or force the compiler to use masked instructions. There are 4 issues ( = paths) costing 1 point each.4
[DA] Low iteration count (8.21 < 10) - Perform full unroll. Use compiler pragmas. Use PGO/FDO compiler options. Force compiler to use masked instructions. This issue costs 5 points.5
Data Access Issues+4
[SA] Presence of indirect accesses - Use array restructuring or gather instructions to lower the cost. There are 1 issues ( = indirect data accesses) costing 4 point each.4
Vectorization Roadblocks+8
[SA] Several paths (4 paths) - Simplify control structure or force the compiler to use masked instructions. There are 4 issues ( = paths) costing 1 point each.4
[SA] Presence of indirect accesses - Use array restructuring or gather instructions to lower the cost. There are 1 issues ( = indirect data accesses) costing 4 point each.4
Loop 15079 - AVBP_V7.16.0.KRAKEN+Execution Time: 0 % - Vectorization Ratio: 0.00 % - Vector Length Use: 10.31 %
Control Flow Issues+1002
[SA] Too many paths (1003 paths) - Simplify control structure. There are 1003 issues ( = paths) costing 1 point, limited to 1000.1000
[SA] Non innermost loop (Outermost) - Collapse loop with innermost ones. This issue costs 2 points.2
Data Access Issues+2
[SA] More than 20% of the loads are accessing the stack - Perform loop splitting to decrease pressure on registers. This issue costs 2 points.2
Vectorization Roadblocks+1002
[SA] Too many paths (1003 paths) - Simplify control structure. There are 1003 issues ( = paths) costing 1 point, limited to 1000.1000
[SA] Non innermost loop (Outermost) - Collapse loop with innermost ones. This issue costs 2 points.2
Loop 4884 - AVBP_V7.16.0.KRAKEN+Execution Time: 0 % - Vectorization Ratio: 0.00 % - Vector Length Use: 9.38 %
Control Flow Issues+15
[SA] Too many paths (9 paths) - Simplify control structure. There are 9 issues ( = paths) costing 1 point each with a malus of 4 points.13
[SA] Non innermost loop (Outermost) - Collapse loop with innermost ones. This issue costs 2 points.2
Data Access Issues+2
[SA] More than 20% of the loads are accessing the stack - Perform loop splitting to decrease pressure on registers. This issue costs 2 points.2
Vectorization Roadblocks+15
[SA] Too many paths (9 paths) - Simplify control structure. There are 9 issues ( = paths) costing 1 point each with a malus of 4 points.13
[SA] Non innermost loop (Outermost) - Collapse loop with innermost ones. This issue costs 2 points.2
Loop 21754 - AVBP_V7.16.0.KRAKEN+Execution Time: 0 % - Vectorization Ratio: 0.00 % - Vector Length Use: 6.25 %
Loop Computation Issues+5
[SA] Peel/tail loop, considered having a low iteration count - Perform full unroll. Force compiler to use masked instructions. This issue costs 5 points.5
Control Flow Issues+5
[SA] Peel/tail loop, considered having a low iteration count - Perform full unroll. Force compiler to use masked instructions. This issue costs 5 points.5
Loop 21746 - AVBP_V7.16.0.KRAKEN+Execution Time: 0 % - Vectorization Ratio: 0.00 % - Vector Length Use: 7.92 %
Control Flow Issues+47
[SA] Too many paths (41 paths) - Simplify control structure. There are 41 issues ( = paths) costing 1 point each with a malus of 4 points.45
[SA] Non innermost loop (InBetween) - Collapse loop with innermost ones. This issue costs 2 points.2
Data Access Issues+2
[SA] More than 20% of the loads are accessing the stack - Perform loop splitting to decrease pressure on registers. This issue costs 2 points.2
Vectorization Roadblocks+47
[SA] Too many paths (41 paths) - Simplify control structure. There are 41 issues ( = paths) costing 1 point each with a malus of 4 points.45
[SA] Non innermost loop (InBetween) - Collapse loop with innermost ones. This issue costs 2 points.2
Loop 3809 - AVBP_V7.16.0.KRAKEN+Execution Time: 0 % - Vectorization Ratio: 33.33 % - Vector Length Use: 25.00 %
Loop Computation Issues+7
[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
[DA] Low iteration count (4 < 10) - Perform full unroll. Use compiler pragmas. Use PGO/FDO compiler options. Force compiler to use masked instructions. This issue costs 5 points.5
Control Flow Issues+5
[DA] Low iteration count (4 < 10) - Perform full unroll. Use compiler pragmas. Use PGO/FDO compiler options. Force compiler to use masked instructions. This issue costs 5 points.5
Loop 21747 - AVBP_V7.16.0.KRAKEN+Execution Time: 0 % - Vectorization Ratio: 0.00 % - Vector Length Use: 6.25 %
Control Flow Issues+13
[SA] Too many paths (9 paths) - Simplify control structure. There are 9 issues ( = paths) costing 1 point each with a malus of 4 points.13
Data Access Issues+2
[SA] More than 20% of the loads are accessing the stack - Perform loop splitting to decrease pressure on registers. This issue costs 2 points.2
Vectorization Roadblocks+13
[SA] Too many paths (9 paths) - Simplify control structure. There are 9 issues ( = paths) costing 1 point each with a malus of 4 points.13
Loop 33978 - AVBP_V7.16.0.KRAKENExecution Time: 0 % - Vectorization Ratio: 0.00 % - Vector Length Use: 12.50 %
Loop 21753 - AVBP_V7.16.0.KRAKEN+Execution Time: 0 % - Vectorization Ratio: 37.21 % - Vector Length Use: 14.83 %
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+52
[SA] Too many paths (46 paths) - Simplify control structure. There are 46 issues ( = paths) costing 1 point each with a malus of 4 points.50
[SA] Non innermost loop (InBetween) - Collapse loop with innermost ones. This issue costs 2 points.2
Data Access Issues+6
[SA] Presence of special instructions executing on a single port (INSERT/EXTRACT, BROADCAST) - Simplify data access and try to get stride 1 access. There are 4 issues (= instructions) costing 1 point each.4
[SA] More than 20% of the loads are accessing the stack - Perform loop splitting to decrease pressure on registers. This issue costs 2 points.2
Vectorization Roadblocks+52
[SA] Too many paths (46 paths) - Simplify control structure. There are 46 issues ( = paths) costing 1 point each with a malus of 4 points.50
[SA] Non innermost loop (InBetween) - Collapse loop with innermost ones. This issue costs 2 points.2
Inefficient Vectorization+4
[SA] Presence of special instructions executing on a single port (INSERT/EXTRACT, BROADCAST) - Simplify data access and try to get stride 1 access. There are 4 issues (= instructions) costing 1 point each.4
Loop 3802 - AVBP_V7.16.0.KRAKEN+Execution Time: 0 % - Vectorization Ratio: 33.33 % - Vector Length Use: 16.67 %
Data Access Issues+12
[SA] Presence of constant non unit stride data access - Use array restructuring, perform loop interchange or use gather instructions to lower a bit the cost. There are 2 issues ( = data accesses) costing 2 point each.4
[SA] Presence of indirect accesses - Use array restructuring or gather instructions to lower the cost. There are 1 issues ( = indirect data accesses) costing 4 point each.4
[SA] Presence of special instructions executing on a single port (INSERT/EXTRACT) - Simplify data access and try to get stride 1 access. There are 4 issues (= instructions) costing 1 point each.4
Vectorization Roadblocks+8
[SA] Presence of constant non unit stride data access - Use array restructuring, perform loop interchange or use gather instructions to lower a bit the cost. There are 2 issues ( = data accesses) costing 2 point each.4
[SA] Presence of indirect accesses - Use array restructuring or gather instructions to lower the cost. There are 1 issues ( = indirect data accesses) costing 4 point each.4
Inefficient Vectorization+4
[SA] Presence of special instructions executing on a single port (INSERT/EXTRACT) - Simplify data access and try to get stride 1 access. There are 4 issues (= instructions) costing 1 point each.4
×