User Guide

  • 2020
  • 05/04/2020
  • Public Content
Contents

baseline-result

Propagate states and annotations from a specified baseline result when performing analysis or generating a report.

Syntax

-baseline-result
<PATH>
Arguments
A string containing the PATH/name for the
baseline result.
This may be an absolute path, or a path relative to the current working directory.
Default
When performing analysis, problem states and annotations from the most recently created result of the same type are carried forward to the new result.
Description
Use the
baseline-result
action-option to specify a result other than the most recently created result of this type as the baseline for a new collection. You can also specify a baseline when finalizing a result or generating a report. Problem states and annotations from the specified baseline result are carried forward to the new result, newly finalized result, or report.
For debugging, run an analysis to create your baseline result, and then use the
create-breakpoints
action to add one or more breakpoints to your baseline result. In subsequent analysis runs, use the
debug-this
option to switch to debug mode, and specify the baseline result with the breakpoints. The debugger will break at the defined breakpoints. When ready to resume collection, use the
command
action.
Whatever type of analysis is used to create the baseline result, the results will align most closely if the same type is used when generating a subsequent result. A similar type can also be used, though an increased or reduced level of analysis will create some mismatches.
In this example, the
mi3
,
Locate Memory Problems
, analysis type is used when analyzing
MyApp
and for subsequent analysis runs that use this baseline result.
To create the result that you want to use as a baseline, perform a memory analysis on
MyApp
and save the result in the
mi3_baseline
result directory.
$ inspxe-cl -collect mi3 -result-dir ./mi3_baseline -- ./MyApp
Create a breakpoint for problem P1 in the baseline result.
$ inspxe-cl -create-breakpoints P1 -result-dir ./mi3_baseline
Perform another analysis in debug mode by specifying the
debug-this
option so that the debugger breaks at the P1 breakpoint created in the previous step. The
baseline-result
option passes in the baseline result from the
mi3_baseline
result directory. Since the result directory for the new analysis result was not specified, it is written to a default-named result directory under the current working directory.
$ inspxe-cl -collect mi3 -debug-this -baseline-result ./mi3_baseline -- ./MyApp

Product and Performance Information

1

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