options

bench_mos - 2024-02-13 11:52:43 - MAQAO 2.19.0

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

▼Stylizer  

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

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

[ 2.81 / 3 ] Optimization level option is correctly used

[ 2.81 / 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.81 / 3 ] Architecture specific option -march=native 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

▼Optimizer

Loop IDModuleAnalysisPenalty ScoreCoverage (%)Vectorization
Ratio (%)
Vector Length
Use (%)
►434libqmckl.so.0.0.0Inefficient vectorization.255.7410050
○[SA] Inefficient vectorization: use of shorter than available vector length - Force compiler to use proper vector length. CAUTION: use of 512 bits vectors could be more expensive than 256 bits on some processors. Use intrinsics (costly and not portable). The issue costs 2 points.2
○Warning! There is no dynamic data for this loop. Some checks can not been performed.0
►380libqmckl.so.0.0.0Inefficient vectorization.226.5510050
○[SA] Inefficient vectorization: use of shorter than available vector length - Force compiler to use proper vector length. CAUTION: use of 512 bits vectors could be more expensive than 256 bits on some processors. Use intrinsics (costly and not portable). The issue costs 2 points.2
○Warning! There is no dynamic data for this loop. Some checks can not been performed.0
►436libqmckl.so.0.0.0Partial or unexisting vectorization - Use pragma to force vectorization and check potential dependencies between array access.121.597540.63
○[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 3 issues ( = data accesses) costing 2 point each.6
○[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] Several paths (2 paths) - Simplify control structure or force the compiler to use masked instructions. There are 2 issues ( = paths) costing 1 point each.2
►36libqmckl.so.0.0.0Partial or unexisting vectorization - Use pragma to force vectorization and check potential dependencies between array access.10031.5229.0221.22
○[SA] Too many paths (at least 1000 paths) - Simplify control structure. There are at least 1000 issues ( = paths) costing 1 point.1000
○[SA] Non innermost loop (InBetween) - Collapse loop with innermost ones. This issue costs 2 points.2
○[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
○Warning! Some static analysis are missing because the loop has too many paths. Use a higher value for --maximal_path_number option.0
►431libqmckl.so.0.0.0Inefficient vectorization.21.2510050
○[SA] Inefficient vectorization: use of shorter than available vector length - Force compiler to use proper vector length. CAUTION: use of 512 bits vectors could be more expensive than 256 bits on some processors. Use intrinsics (costly and not portable). The issue costs 2 points.2
○Warning! There is no dynamic data for this loop. Some checks can not been performed.0
►433libqmckl.so.0.0.0Partial or unexisting vectorization - Use pragma to force vectorization and check potential dependencies between array access.311.1833.6225.11
○[SA] Too many paths (25 paths) - Simplify control structure. There are 25 issues ( = paths) costing 1 point each with a malus of 4 points.29
○[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
►32bench_mosInefficient vectorization.20.8610050
○[SA] Inefficient vectorization: use of shorter than available vector length - Force compiler to use proper vector length. CAUTION: use of 512 bits vectors could be more expensive than 256 bits on some processors. Use intrinsics (costly and not portable). The issue costs 2 points.2
○Warning! There is no dynamic data for this loop. Some checks can not been performed.0
►106libqmckl.so.0.0.0Partial or unexisting vectorization - Use pragma to force vectorization and check potential dependencies between array access.10030.8128.7520.91
○[SA] Too many paths (at least 1000 paths) - Simplify control structure. There are at least 1000 issues ( = paths) costing 1 point.1000
○[SA] Non innermost loop (InBetween) - Collapse loop with innermost ones. This issue costs 2 points.2
○[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
○Warning! Some static analysis are missing because the loop has too many paths. Use a higher value for --maximal_path_number option.0
►37libqmckl.so.0.0.0Partial or unexisting vectorization - Use pragma to force vectorization and check potential dependencies between array access.2250.6237.9625.69
○[SA] Too many paths (219 paths) - Simplify control structure. There are 219 issues ( = paths) costing 1 point each with a malus of 4 points.223
○[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
►435libqmckl.so.0.0.0Inefficient vectorization.40.610050
○[SA] Inefficient vectorization: use of shorter than available vector length - Force compiler to use proper vector length. CAUTION: use of 512 bits vectors could be more expensive than 256 bits on some processors. Use intrinsics (costly and not portable). The issue costs 2 points.2
○[SA] Inefficient vectorization: use of masked instructions - Simplify control structure. The issue costs 2 points.2
○Warning! There is no dynamic data for this loop. Some checks can not been performed.0
×