options

spmxv.exe - 2024-10-07 16:57:17 - MAQAO 2.20.9

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

▼Stylizer  

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

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

[ 3 / 3 ] Optimization level option is correctly used

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

Functions without compilation information (typically not compiled with -g) cumulate 0.01% 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.

[ 3.00 / 3 ] Architecture specific option -march=native is used

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

▼Optimizer

Loop IDAnalysisPenalty Score
►Loop 16 - spmxv.exe+Execution Time: 50 % - Vectorization Ratio: 100.00 % - Vector Length Use: 35.00 %
►Data Access Issues+8
○[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 expensive instructions (GATHER/SCATTER) - Use array restructuring. There are 1 issues (= instructions) costing 4 points each.4
►Vectorization Roadblocks+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 expensive instructions (GATHER/SCATTER) - Use array restructuring. There are 1 issues (= instructions) costing 4 points each.4
►Loop 14 - spmxv.exe+Execution Time: 18 % - Vectorization Ratio: 31.88 % - Vector Length Use: 15.94 %
►Loop Computation Issues+6
○[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
○[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+6
○[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] Non innermost loop (InBetween) - Collapse loop with innermost ones. This issue costs 2 points.2
►Data Access Issues+3
○[SA] Presence of special instructions executing on a single port (INSERT/EXTRACT, SHUFFLE/PERM) - Simplify data access and try to get stride 1 access. There are 1 issues (= instructions) costing 1 point each.1
○[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+6
○[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] Non innermost loop (InBetween) - Collapse loop with innermost ones. This issue costs 2 points.2
►Inefficient Vectorization+1
○[SA] Presence of special instructions executing on a single port (INSERT/EXTRACT, SHUFFLE/PERM) - Simplify data access and try to get stride 1 access. There are 1 issues (= instructions) costing 1 point each.1
►Loop 15 - spmxv.exe+Execution Time: 16 % - Vectorization Ratio: 0.00 % - Vector Length Use: 12.50 %
►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
►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+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 13 - spmxv.exe+Execution Time: 0 % - Vectorization Ratio: 0.00 % - Vector Length Use: 7.69 %
►Control Flow Issues+6
○[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] 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+6
○[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] Non innermost loop (InBetween) - Collapse loop with innermost ones. This issue costs 2 points.2
►Loop 12 - spmxv.exe+Execution Time: 0 % - Vectorization Ratio: 5.00 % - Vector Length Use: 8.75 %
►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+16
○[SA] Presence of calls - Inline either by compiler or by hand and use SVML for libm calls. There are 4 issues (= calls) costing 1 point each.4
○[SA] Too many paths (6 paths) - Simplify control structure. There are 6 issues ( = paths) costing 1 point each with a malus of 4 points.10
○[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+16
○[SA] Presence of calls - Inline either by compiler or by hand and use SVML for libm calls. There are 4 issues (= calls) costing 1 point each.4
○[SA] Too many paths (6 paths) - Simplify control structure. There are 6 issues ( = paths) costing 1 point each with a malus of 4 points.10
○[SA] Non innermost loop (Outermost) - Collapse loop with innermost ones. This issue costs 2 points.2
×