• 9.1 Update 2
  • 11/11/2015
  • Public Content

Summary


You have completed the
Detecting and Resolving Errors with MPI Correctness Checker
tutorial. The following is the summary of important things to remember when using this functionality to check your MPI application for errors.
Step
Tutorial Recap
Key Tutorial Take-aways
Configuration options overview
Reviewed the configuration options that control the correctness checking functionality.
You can configure the correctness checking process by adjusting the necessary settings according to your needs.
Resolving the data type mismatch error
  • Ran an application with the data type mismatch error to detect the cause.
  • Used the correctness checker messages to locate and eliminate the problem.
You can use the correctness checker command-line messages to resolve the reported problems.
Resolving the deadlock error
  • Ran an application with the deadlock error and created its trace file to detect the cause of the problem.
  • Used the correctness checker messages and Intel® Trace Analyzer Source View to locate and eliminate the problem.
You can:
  • Store source code locations in trace file to easily find problem causes.
  • View and analyze the reported problems using Intel® Trace Analyzer GUI.
 

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 reserverd 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