User Guide



Collect loop trip counts data during Trip Counts & FLOP analysis.


On (trip-counts)
Actions Modified
Use the option, which allows you to dynamically identify the number of times loops are invoked and executed, to:
  • Detect loops with too-small trip counts and trip counts that are not a multiple of vector length.
  • Analyze parallelism granularity more deeply.
Disabling can decrease analysis overhead.
Run a Trip Counts & FLOP analysis. Collect trip counts, FLOP, and call stack data.
$ advixe-cl --collect=tripcounts --flop --stacks --project-dir=./advi -- ./bin/myApplication
Run a Trip Counts & FLOP analysis. Collect only FLOP data.
$ advixe-cl --collect=tripcounts --no-trip-counts --project-dir=./advi --search-dir src:=./src -- ./bin/myApplication

Product and Performance Information


Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.

Notice revision #20110804